Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Disabling Existing Constraints and Index dropped
Read below for my single comment
Richard Foote wrote:
> Hi Phil, > > Yes, Oracle will create the index automatically again for you. A couple > of points though. > > Firstly, it's not good practice to just create or enable a Primary Key > or Unique key and let Oracle just create the index on its own. I would > strongly recommend the use of the USING INDEX clause to control how the > index is created (such as it's name and tablespace). Note 9i allows you > to define the entire create index syntax when creating/enabling these > constraints. > > Also note Oracle doesn't necessarily create or drop the indexes > associated with the constraint. If the index being used by Oracle is non > unique (possible for deferrable constraints) then the index is not > dropped automatically (although 9i can override this default behavior). > If an existing index could be used to police a new constraint (in that > the leading columns of an existing index match the column constraints), > then Oracle will use the existing index and will not create an > unnecessary index. > > So there's a fair bit to all this :)
Well then u loose uniqueness in your index and you incur read costs for unique searches. Not much but why should you ?
> > Cheers > > Richard > > > phil wrote:
![]() |
![]() |