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 |
|
inbs
Aged Yak Warrior
860 Posts |
 Posted - 2009-11-01 : 04:19:57
|
| hi,i have a table with 5 miliom rows, every day i delete 50K rows and insert 50K rows.i need to get results in a few seconds. so i added a culstered index on the column OrderNumber.Is it right to rubild the index on this talbe?(i understand ,if i delete/insert many rows in table every day ,so it is not recommended to use index in table,because i need rebuild index on that table and it take a long time) |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Pradip
Starting Member
32 Posts |
Posted - 2009-11-02 : 00:38:35
|
| If your delete and insert goes in specific range of ordernumber then you can use table partition for those range which will again increase performance.Keep index on ordernumber, let's use update stats regularly in less peak time(night hours) after you finished much insert and delete operations.pradipjain |
 |
|
|
inbs
Aged Yak Warrior
860 Posts |
Posted - 2009-11-02 : 01:30:04
|
| tkizerif my table is 15M rows is still small table?and index should rebuild quickly?? |
|
|
|
|
|
|
table and index