Hi, we still have problems getting our udate of the statistics we have Sapdb 7.4.3.32/7.4.3.31 running on Linux Redhat and Suse. In our backup procedure we have
util_connect util_execute check data except index sql_updatestat backup_start pipe data
The proposed alternative was to use
UPDATE STATISTICS <tablename> ESTIMATE SAMPLE 49 PERCENT
or any other percentage value. The latter updatestatistics saves us a lot of time but with the sql-command we do not get the same query performance after millions of insertion as with the dbmcli command sql_updatestat. In the release notes of 7.4.3.32 I read something about problems with very large tables befor this version but after an upgrade we have still problems to get the performance. on very large tables (> 1GByte/100Million Rows)
- Are there essential improvements on that side for the MaxDB product? - How can I make an estimation on the needed time for one run of the sql_updatestat command? - If I'm killing the process of the sql_updatestat command is the data which it produced until then lost due to the fact that it works in a transaction? - If that rollback is done, why?
Thanx for response
Georg
This e-mail may contain trade secrets or privileged, undisclosed or otherwise confidential information. If you are not the intended recipient and have received this e-mail in error, you are hereby notified that any review, copying or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal from your system. Thank you for your co-operation.
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
