Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
WJHamel
Aged Yak Warrior
651 Posts |
 Posted - 2012-07-18 : 19:41:01
|
| So i have this HUGE data conversion that i'm working on. My scripts are replete with Inner Joins. Overall, many of the joins are taking hours to run. Most of the columns it's reading from have in excess of 200,000 rows, some as many as 700,000. I've indexed as many of those columns as i've had time to at this point, but it's pretty clear that i need to index many more of these columns from these tables.Is there ANY quicker way to create indexes for ALL columns in a given table without writing code for EACH line? Maybe a 3rd party app that will look at those columns and create an index with a default name? |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-07-18 : 20:17:41
|
| why should you create index on ALL columns in a table? You need to analyse and add once those indexes which your queries should be able to utilise. Use database tuning advisor to get an idea on queries to be tuned. Adding too many indexes will also cause issues as your DML statement will become slower------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
|
|
|
Building indexes