Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...
SQL Server Forum / DB Engine / SQL Server / March 2008

Tip: Looking for answers? Try searching our database.

Updating Statistics

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Tom Frost - 10 Mar 2008 17:46 GMT
I have a database which has logical fragmentation in some of the tables.

I have scripts that now will run an update_statisitics with fullscan on all
the objects.
I also have a job that perfroms a dbcc dbreindex on the indexes if the
logical or physical scan density returned from dbcc showcontig is above
certain thresholds.

My question is would it make any difference in running an update-statistics
with fullscan prior to any reindexing tasks  instead of running update stats
after the dbcc dbreindex, or does it not matter? Would the dbcc showcontig
benefit from having an updated statistics with full scan performed with all
the statistics updated be preferable?
Reply to this Message
Tom Moreau - 10 Mar 2008 20:22 GMT
When an index is built/rebuilt, the stats are completely done with a
fullscan, so doing both doesn't buy you anything.

Signature

  Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON   Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

I have a database which has logical fragmentation in some of the tables.

I have scripts that now will run an update_statisitics with fullscan on all
the objects.
I also have a job that perfroms a dbcc dbreindex on the indexes if the
logical or physical scan density returned from dbcc showcontig is above
certain thresholds.

My question is would it make any difference in running an update-statistics
with fullscan prior to any reindexing tasks  instead of running update stats
after the dbcc dbreindex, or does it not matter? Would the dbcc showcontig
benefit from having an updated statistics with full scan performed with all
the statistics updated be preferable?
Reply to this Message
Tom Frost - 10 Mar 2008 20:57 GMT
does updating the statistics provide any additional information regarding
potential fragementation that would be used within dbcc shpwcontig?

> When an index is built/rebuilt, the stats are completely done with a
> fullscan, so doing both doesn't buy you anything.
[quoted text clipped - 12 lines]
> benefit from having an updated statistics with full scan performed with all
> the statistics updated be preferable?
Reply to this Message
Tibor Karaszi - 10 Mar 2008 21:33 GMT
Nope. There is no fragmentation level info in the statistics (no "physical state").

Signature

Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi

> does updating the statistics provide any additional information regarding
> potential fragementation that would be used within dbcc shpwcontig?
[quoted text clipped - 15 lines]
>> benefit from having an updated statistics with full scan performed with all
>> the statistics updated be preferable?
Reply to this Message
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage
Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.