February 18, 2010 at 10:27 am
WOW.. Now the query ran for 0 MS from 16 sec.
Gail thanks for your help. The index really helped..
Regards
Moosa
February 23, 2010 at 9:31 am
Hi Gila,
I am having a few questions here. Could you please describe why we need to include these columns on the index.
1. Will the include columns on the index will make any performance degradation on other queries.
2.The index creation took 2 hours to complete, it will make any changes on the re-index process.
February 23, 2010 at 9:32 am
Hi Gila,
I am having a few questions here. Could you please describe why we need to include these columns on the index.
1. Will the include columns on the index will make any performance degradation on other queries.
2.The index creation took 2 hours to complete, it will make any changes on the re-index process.
February 23, 2010 at 10:52 am
moosamca (2/23/2010)
I am having a few questions here. Could you please describe why we need to include these columns on the index.
Because the columns are in the select clause and too many rows are selected to make key lookups a viable option
1. Will the include columns on the index will make any performance degradation on other queries.
One index shouldn't notably affect anything. You can test update/insert/deletes before and after to check
2.The index creation took 2 hours to complete, it will make any changes on the re-index process.
2 hours? That's a lot. how many rows in the table?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply