RE: stats/checks in 24X7 environment ?

________________________________________ From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of infx dba Sent: Tuesday, December 12, 2006 3:06 PM To: informix-list@iiug.org Subject: stats/checks in 24X7 environment ? Hi, Need to know when you'll run stats and onchecks in a 24X7 environment, in the organization where i am working we alternate stats and checks every sunday, during this time we also have users connecting to the database and run jobs. replication is not an option for us, need to know when you'll run stats and checks in the 24X7 environment ? Thanks ------------------------------------------- I assume you mean update statistics and oncheck? Or are you talking about instance stats (table sizes, I/O rates, etc)? In any case, update stats will chew up some resources (disk I/O, memory, etc), but is pretty good about not locking things. I would suspect that unless your data is changing very fast indeed doing a thorough update every two weeks is probably sufficient. Look into Art's dostats script (on the IIUG software repository) -- it's a great way to automate this. Some oncheck statements can lock things in certain situations (even when IDS support tells you it won't, but that's another story). That one I'd be careful of if you want to avoid user impact. What is it you're looking to check? Generally I don't bother unless I suspect there may be a problem. It seems to me that if you're running a 24x7 environment then replication should be made into an option, or you risk significant downtime and possible data loss in the event of a disaster. DC