Re: INDEX Use. How?

Karen,

I would strongly discourage you from granting 'Create Any Index' to your user community.

In UNIX, I prefer to provide the user community with a ksh script which does the following:

1. Accepts one parameter, which is the filename of an index creation script.
2. Copies that script to an archive.
3. Interrogates the invoking shell for user and group id, then records them in an ORACLE table.
4. Executes the script as a dedicated user.
5. Emails the invoker and the duty DBA with a short log report.

The script is executable by anyone in a dedicated UNIX group, but readable only by the UNIX login oradba. Requiring all creates to be done via scripts allows better auditing, but also offers the users some automatic documentation.

If you provide a create index skeleton script which includes a tablespace identifier and a storage clause, most users will pick it up quickly. Having the archive lets you monitor compliance, monitor space usage, and identify problem users more quickly.

Hope this helps,
Don Humberson

Karen Byrd wrote:

> We want to establish two tablespaces(one for tables and the other for indices).
> If we give users the privileges to create an index via "creat index"
> or create tables using a primary key how can we guarantee where the
> indices are created by default? In other words we want all indices to
> reside in the tablespace we are going to set up for them every time.
>
> TIA
>
> --
> Karen Byrd
> Univ. of PA, School of Med.
> Computing and Information Technology
> byrd_at_mscf.med.upenn.edu
Received on Tue Feb 17 1998 - 00:00:00 CST