Re: Wierd Table -- Aaargh!

Daily is adequate for most medium size databases (say 1-500 MB). Hourly would only be necessary on a really volatile and mostly empty database; and would probably only ever be relevant for one or two tables in a database. In fact, if you get into gigabyte size databases, you don't necessarily run UPDATE STATISTICS daily because it takes too long and the database doesn't change enough to warrant the time it takes. You also start looking hard at only updating the statistics for one table at a time, rather than the whole database, and having a complex schedule for when each table is done. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> }From: pete@afc.org (Pete Stiglich) }Subject: Re: Wierd Table -- Aaargh! }Date: 18 Aug 1994 19:45:27 GMT }X-Informix-List-Id: <news.8253> } }Pete Stiglich (pete@afc.org) wrote: }: Hello, I am having some really strange problems with one table. JUST that }:table. Occasionaly, users will complain saying that the order entry program }: is bogging down. Invariably, it is because of this ONE table. A query that }: normally takes a second will take 10. } }: It is using a unique index on 3 columns for the query. I've tried dropping }:& recreating the index, clusturing it, bchecking the table & nothing works. }: The only thing that gets it back to normal is unloading the table, dropping }: it and recreating and reloading. } }: There doesn't seem to be any pattern as to when it will happen. Sometimes }: it will be fine for a month, sometimes for a week. I've replaced the }: disk it was on, for other reasons, so I don't think thats the problem. It }: only happens on this table. It is heavily used, but there are other tables }: with more usage. } }Thanks to everyone who responded. The overall consensus was that I should }check how often I am updating statistics. How often should it be run? }Daily? Hourly? } }Thanks }Pete