RE: Disabling indexes - temporarily

[Edward Shevtsov]

Title: Сообщение

Marul,   have a look at table partition and ALTER TABLE EXCHANGE PARTITION WITH TABLE statement. Using the combination of these approaches you're able to limit index rebuilding with a few partitions if your indexes are local. At least you will be able to separate I/O.   Regards, Ed     -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Marul Mehta Sent: Monday, September 02, 2002 2:38 PM To: Multiple recipients of list ORACLE-L Subject: Re: Disabling indexes - temporarily Thanks Naveen, Lets forget about the statistics and performance, but I have such type of requirenment than is there any way out ?   Marul. ----- Original Message ----- From: Naveen Nahata To: Multiple recipients of list ORACLE-L Sent: Saturday, August 31, 2002 11:58 PM Subject: RE: Disabling indexes - temporarily Firstly, you are only inserting 100-400 records daily, which is not a big deal. Even if there was a way to stop the indexes from getting updated, it won't increase the performance by a noticable amount.   Secondly, there is no way(as far as i know) to make the indexes READ-ONLY with the table in READ-WRITE mode.   Thirdly, rebuilding 20 indexes on a table with 1 million record will take a long time, in comparison updation by 100-400 records is nothing.   It neither feasible nor advisable.   Naveen -----Original Message----- From: Marul Mehta [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 31, 2002 11:08 PM To: Multiple recipients of list ORACLE-L Subject: Disabling indexes - temporarily Hi all,   Need to know if the following is possible in Oracle(any version):-   I have a table of around     (a) 30 Columns     (b) 20 out of 30 are indexed     (c) around 1 million (1,000,000) records.   Most of the time there will be heavy reads (select queries) on this table except for some 100-400 records to be inserted in a day. The newly inserted records will not be selected by the queries for the next 24 hours (this is based on some business logic), thats for sure.   Now the problem is when ever a record(s) is inserted the entire bunch of indexes is updated/rebuild by the Oracle which considerably slows down the throughput of the system during that period of time (until all indexes are updated).   Can we have a solution whereby indexes should not be updated when a record(s) is inserted, because I know that these records will not be the part of the query for the next 24 hrs. The indexes will be re-built manually/scheduled during the off-peak hours once a day. In this way, the next day, new records inserted a day before will be ready to be fetched by the queries.   Note- I can't put my indexes offline not for a single minute during peak hours.   Any clues?   TIA, Marul.