February 11, 2010 at 8:45 am
I have a very large and wide SQL table (I inherited).
I am in need of indexing this beast of a table.
Problem is (other then not being normalized) that the table has 469 rows and I know SQL05 will not allow me to index every column.
Worth noting this is a report table.
I thought there was a way to have SQL tell me which of the 468 columns are the most heavily used? Figured I'd use a covering type of indexing schema.
February 11, 2010 at 8:50 am
Are you talking about the database engine tuning advisor?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
February 11, 2010 at 8:53 am
No...I realize I could (and maybe should) start a trace on the table...and then optimize it using ETA. Unless I missing something in ETZ I could use.
But I thought I read somewhere that SQL05 had the ability to tell me the most used columns in a table? I'm assuming some columns are rarely used for these reports.
February 11, 2010 at 9:37 am
missing index dmv is what I was looking for..
February 11, 2010 at 9:44 am
krypto69 (2/11/2010)
missing index dmv is what I was looking for..
Just be smart with that. It'll give you overlapping recommendations that end up being redundant in many cases.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply