March 9, 2010 at 10:03 pm
If the table customer had millions of rows, what would you do to improve searches based on last name ?
March 9, 2010 at 10:39 pm
Create index, Use DTA to check which index will improve performance.
March 10, 2010 at 5:44 pm
I agree... depending on what the search criteria is, an index can help a lot.
A word of caution on DTA... it can and will frequently lead you down the primrose path. Don't just blindly take it's recommendations because it's frequently wrong especially when you have a column with very low cardinality in your query. Although it may give you and index to make your SELECTs lightning fast, that same index can eat the face off your database for INSERTs and UPDATES when the index splits to accomodate new rows. We had such an index on one of our system... it caused 30,000 reads for each insert.
Be very wary of DTA recommendations without full load testing.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2010 at 12:24 am
kaladharreddy15 (3/9/2010)
If the table customer had millions of rows, what would you do to improve searches based on last name ?
It depends on the searches. Full-text index maybe? Add a computed column based on a hash function and index that? As I say, it depends.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
March 22, 2010 at 11:37 am
Jeff Moden (3/10/2010)
...A word of caution on DTA...Although it may give you an index to make your SELECTs lightning fast, that same index can eat the face off your database for INSERTs and UPDATES...
Heh... You've GOTTA add that to your sig...
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply