June 9, 2011 at 3:23 pm
Another index question:
I have a static table. The data is not updated. Table is a snapshot for archival reporting.
It is roughly 6+ million rows and 200 fields. The fields contain text, amounts, and dates.
The table's first column is a unique id.
Users can and will search the table on any of the 200 fields, and a combination of fields.
My thought was to create a clustered index on the unique ID field. Then create a few more non-clustered indexes (with included columns) based on the most frequent queries.
Knowing that with so many fields I will never be able to cover all possible queries with an index.
Am I on the right path, or would anyone recommend a better solution?
June 9, 2011 at 4:28 pm
Might I suggest a little reading to help you find the right path to follow.
http://www.sql-server-performance.com/2009/identify-missing-indexes-using-sql-server-dmvs/
and/or
http://blogs.msdn.com/b/bartd/archive/2007/07/19/are-you-using-sql-s-missing-index-dmvs.aspx
Right here on SSC
June 10, 2011 at 1:27 pm
Thanks for the links. They are very helpful and useful.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply