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 |
|
Christina Agyeman
Starting Member
15 Posts |
 Posted - 2002-07-30 : 12:15:08
|
| What are the disadvantages of using a clustered index. We have a table that we would perform 500,000 inserts and 40,000 deletes of rows per day. Will creating clustered index on this table cause fragmentation. |
|
|
royv
Constraint Violating Yak Guru
455 Posts |
Posted - 2002-07-30 : 12:21:38
|
| This is an excellent website that gives good advice on performance issues with SQL Server. www.sql-server-performance.com*************************Someone done told you wrong! |
 |
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-07-30 : 13:07:06
|
Any index will cost you on INSERTs and DELETEs. They key is to evaluate the benefits of the index and weight those against the costs...If you never access this table accept to insert into it and delete from it, then leaving it as a heap is your best bet....on the other hand, if you have a table you never select from, why have the table  ...Jay White{0} |
|
|
|
royv
Constraint Violating Yak Guru
455 Posts |
Posted - 2002-07-30 : 13:29:35
|
| If you mean 500,000 inserts at one time, meaning one insert with 500,000 records to be inserted, then Page47 is correct. If you mean 500,000 inserts, one record inserted at a time, then you should add a clustered index on the table, because this will prevent hotspots in a heap.*************************Someone done told you wrong! |
|
|
|
|
|
|
|
|
Clustered Index