January 6, 2012 at 7:47 am
Where the 1000 pages actually comes from... & the guy who wrote that code at MS!
January 6, 2012 at 7:50 am
Guras (1/5/2012)
rfr.ferrari (1/5/2012)
how many time to execute the select command in table?It takes about a second to return all the 361 rows.
If you are retrieving the whole population of the table (361 rows in this case) you better pray execution plan DO NOT rely on indexes but on a Full Table Scan.
Having said that, I agree with a previous post in the sense that on a 361 rows table fragmentation really don't matter.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.January 6, 2012 at 11:15 am
Ninja's_RGR'us (1/6/2012)
Where the 1000 pages actually comes from... & the guy who wrote that code at MS!
Yeah, Paul Randal's bottom. Ha!
1000 pags is a good a guideline as anything. I wouldn't get married to it though. I sure wouldn't bother for anything less than 100 pages.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 6, 2012 at 11:24 am
Small indexes (I.e. few pages) are scattered because the pages fill in gaps in used extents. It's likely the database engine would incur extra I\O to move pages to make way for the smaller index and this just isn't worth the effort. It's all explained in the SQL server internals books.
Grant Fritchey (1/6/2012)
Yeah, Paul Randal's bottom. Ha!
You've just put me off my dinner 😛
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 6, 2012 at 6:57 pm
Perry Whittle (1/6/2012)
Small indexes (I.e. few pages) are scattered because the pages fill in gaps in used extents. It's likely the database engine would incur extra I\O to move pages to make way for the smaller index and this just isn't worth the effort. It's all explained in the SQL server internals books.Grant Fritchey (1/6/2012)
Yeah, Paul Randal's bottom. Ha!You've just put me off my dinner 😛
So he's keeping you honest about your new-years' resolution. You should thank him! 😎
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply