Weird Behavior

  • I have a table with 10 Million Rows and one Clustered Index -  on CID Column. 

    I do a DBCC SHOWCONTIG on it and the Scan Density is 16%.  I want to recommend doing a DBCC DBREINDEX on that table, and I wanted to show improvement in query performance.

     

    So I did a "SELECT * FROM <Table1> WHERE CID = 12345".  I got the result back in less than 0.01 seconds with 16% Scan Density.  This surprised me, because I thot there would be some lag and will improve to something better after doing a DBCC DBREINDEX.  But if the damn query returns the result set so quickly, what should be my point of argument to convince that -- "Hey we need to do a DBCC DBREINDEX"

     

     

     

     

     

  • 1 row won't take "much" longer. Try fetching 1k rows in a join or a range search then rerun after the reindex, then you should be better off.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply