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 |
|
Sun Foster
Aged Yak Warrior
515 Posts |
 Posted - 2007-03-17 : 15:38:43
|
| Which way is better?1) to insert a million records into a table but keep 15 index column2) drop index, insert a million records and then create index |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2007-03-17 : 15:48:22
|
| I would go for option 2.Peter LarssonHelsingborg, Sweden |
 |
|
|
rockmoose
SQL Natt Alfen
3279 Posts |
Posted - 2007-03-17 : 19:08:21
|
| How many records are in the table to begin with?rockmoose |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-03-17 : 19:43:32
|
| I would keep the index if it is clustered, AND the data being inserted is pre-sorted in PK order.Otherwise I would drop the re-create the index.Might depend on how many MORE records there were in the table to s tart with - as Rocky asks too.Kristen |
|
|
|
Sun Foster
Aged Yak Warrior
515 Posts |
Posted - 2007-03-18 : 10:26:45
|
| All indexes are simple.I used command as below:truncate table mytableinsert... |
|
|
|
rockmoose
SQL Natt Alfen
3279 Posts |
Posted - 2007-03-18 : 19:29:44
|
| Quite often it is good to drop and rebuild the index.But it does depend...If the inserted data is ordered - as Kristen asksRatio of old/new rows - if the table already has many rows rebuilding the whole index might be more costly than updating it while inserting.rockmoose |
|
|
|
|
|
|
Drop index and then create index?