March 17, 2009 at 9:32 am
I run the following on one of my 2005 production databases to try and gather some stats on indexes:
sys.dm_db_index_physical_stats
I believe the table has around 3.4 billion rows. It is partition by month. One problem is that this server is still on SP1.
I'm assuming that there's just too much data and that's causing a memory issue and then timing out the query.
This table is a data warehouse staging table and contains about 10 years worth of data. The database is set to auto update statistics, but I'm showing a last update of 1 1/2 years ago. This data is loaded on a monthly basis.
Is there a reason why SQL would not update statistics on it's own? Is there a way to update statistics on just the current partition? Just a bit confused as to why stats are not being updated on a table that is obviously being updated/inserted with millions of rows each month.
March 17, 2009 at 12:02 pm
I should state this is actually what I run:
SELECT * FROM sys.dm_db_index_physical_stats(db_id, NULL, NULL,NULL,'LIMITED')
Works fine on test, and that's with 54 million records and SP2 installed.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply