November 20, 2004 at 9:58 am
It seems my SQL 2K database is sucking up a lot of extra space. I have rebuilt the indexes including the clustered index. The non-clustered indexes are good, as you can note below. The clustered look like they are hogging some space. Or maybe it isn't .... Thoughts ?
Minimum Length...................... 3,157
dpages ................................. 3,265,564
reserved ............................... 6,682,290
used .................................... 3,372,723
rowcount .............................. 6,531,127
==============================================
Clustered Index
==============================================
DBCC SHOWCONTIG scanning 'sample' table...
Table: 'sample' (1249244051); index ID: 1, database ID: 7
TABLE level scan performed.
- Pages Scanned................................: 3265564
- Extents Scanned..............................: 408860
- Extent Switches..............................: 408859
- Avg. Pages per Extent........................: 8.0
- Scan Density [Best Count:Actual Count].......: 99.84% [408196:408860]
- Logical Scan Fragmentation ..................: 1.53%
- Extent Scan Fragmentation ...................: 1.27%
- Avg. Bytes Free per Page.....................: 1682.0
- Avg. Page Density (full).....................: 79.22%
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
November 29, 2004 at 1:19 pm
Craig,
you say that your clustered index is hogging memory but the Scan Density value of 99.84% says that the data is pretty compact. Perhaps you want to perform a shrink database operation to reclaim some unused disk space. See BOL for details on how to do this.
Ciao!
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply