[EMAIL PROTECTED] wrote: > As I have mentioned on the list on the past... UPDATE > STATISTICS requires lots of slow disk I/O and it locks the > tables. Some of our tables > are large and the lock can last for long periods (30 minutes > or longer for a single table). Yes, this is on professional > 15,000 RPM SCSI hard > drives. > > My question... I'm assuming that UPDATE STATISTICS is doing > is changing some internal pagecount or otherwise. We have 3 > servers all > running with copies / replicas of the same database. Is it > possible that we could run UPDATE STATISTICS on only one > server and duplicate the > results to the other two servers? > > On a related note, if I use loadercli to populate a database > that was sourced from "TABLEXTRACT PAGES" - do I have to run UPDATE > STATISTICS to get it correct - or is that brought over with > the extracted table? The UPDATE STATISTICS seems to take > longer than loading > the data itself :)
There is no way to replicate the optimizer statistics. But you could use the estimate clause of the update statistic command to speed up the process of statistic evaluation. Here are two examples of the syntax update statistics <tabname> estimate sample 10 percent update statistics <tabname> estimate sample 20000 rows For more information see http://www.sapdb.org/7.4/htmhelp/3b/86f067458411d3a98200a0c9449261/frameset.htm Kind regards, Holger SAP Labs Berlin -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
