Re: UPDATE STATISTICS

In article <3366FBAA.1DD0@netcomuk.co.uk>, Ian Goddard <igoddard@netcomuk.co.uk> writes >David Williams wrote: >> >> In article <19970425213301.RAA05883@ladder01.news.aol.com>, Belakimem >> <belakimem@aol.com> writes ><snip> >> >Does anyone have any ideas regarding the logistics of running of UPDATE >> >STATISTICS in a 24 hour environment? >> > >> Yes. Do not do plain update statistics >> >> Use update statistics for table <tablename> and update statistics >> for procedure <procedure name>. >> >> Write scripts to do these and break down the task of doing the whole >> database into several scripts. Each one can be run during 'quiet' >> time on the system. >> > >Alternatively as 4GL or ESQL. Take the names of tables and procs out of >the system catalogue tables. That way your program becomes aware of new >targets to update and you don't have to maintain scripts. > >Ian My plan was NOT to do all the update statistics in one go but run a few each night. I doubt you could do them all in a 24 hours environment - remember update stistics locks the table whilst it runs. I was assume you might have a small window where you could run a few update statistics for table/procs...say 2-215am every night... -- David Williams