Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
TRACEYSQL
Aged Yak Warrior
594 Posts |
Posted - 2007-04-08 : 09:19:08
|
Our databases is heavily used i have seem on some days the data is 7 gig when they run massive reports ..The erp uses Z_ tables for this...I was thinking of turning of the auto statistics on the database andrunning this nightly insteadDBCC UPDATEUSAGE ('DBNAME')Anyone suggest that i do with FULL SCAN each night.Thanks |
|
dinakar
Master Smack Fu Yak Hacker
2507 Posts |
Posted - 2007-04-08 : 11:20:29
|
Whether you should use FULLSCAN or the default percentage depends on your data and the inserts/updates/deletes happening on the table. You could perhaps try with the default and if you have bad query plans, go for FULLSCAN.************************Life is short. Enjoy it.************************ |
|
|
TRACEYSQL
Aged Yak Warrior
594 Posts |
Posted - 2007-04-08 : 17:13:28
|
I may switch to full to see the effects.I look in to the pros and consThanks |
|
|
TRACEYSQL
Aged Yak Warrior
594 Posts |
Posted - 2007-04-08 : 17:39:12
|
In database there is auto create statistics and auto update statisticswhich one is the DBCC UPDATESTATS that i should turn offI put in a maintnenace plan to do 50% optimatization each nightthen which one to turn offThanks |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-09 : 15:54:11
|
DBCC UPDATEUSAGE corrects the rows, used, reserved, and dpages columns of the sysindexes table for tables and clustered indexes. It's different from update statistics. And you can turn off 'auto update statistics' if you like maintenance plan to handle it. |
|
|
|
|
|