Recently I have been stumped by not cliaming unused space correctly even though after delete handful of rows on a table. You may be aware using SP_SPACEUSED will get you details such as : Column name Data type Description database_name nvarchar(128) Name of the current database. database_size varchar(18) Size of the current database in megabytes. ...

This was the question from SSP forums, I’m trying to rebuild few fragmented indexes on a table that is updated on regular basis. The “dbcc showcontig” gave this result: Table: 'Confidential' (999999999); index ID: 5, database ID: 5 LEAF level scan performed. - Pages Scanned................................: 86 - Extents ...

Long ago, not long ago.... No doubt that many of you might have gone through the error above within your SQL environment, also I see many forum posts out there to resolve the issue. The bottom line of this issue is Hardware and no other issue can contribute such a problem. So this is where DBA's role is enhanced to take care of SQL Server hardware ...

DBCC UPDATEUSAGE (0); GO Best practice to use DBCC UPDATEUSAGE i ntermittently and must if you have upgraded the database from SQL 2000 to 2005. The usual working fashion of this DBCC statement is to correct the rows, used pages, reserved pages, leaf pages, and data page counts for each partition in a table or index. If there are no inaccuracies ...