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 |
|
karuna
Aged Yak Warrior
582 Posts |
 Posted - 2005-04-07 : 09:11:00
|
| If I have a clustered index on a table on primary key which has an initial records of a million and monthly record dump of 50K records, and at any point of time there will be close to 300 concurrent users accessing the website, which is again dependent on the database.Whats the performance I again or loss by using Indexes. Should it be a clustered or Non Clustered.Karunakaran |
|
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2005-04-07 : 11:51:36
|
| Indexes exist to improve read performance. A clustered index can give a massive performance gain. I start with a clustered index on any of my big tables. |
 |
|
|
karuna
Aged Yak Warrior
582 Posts |
Posted - 2005-04-08 : 00:01:49
|
| My concern is not only reading performance, When I say 300 concurrent users, atleast of half of that will be some how involved in data manipulation either inserting or updating or some cases even deleting. I like to have a view on an overall performance issue considering all this.Karunakaran |
|
|
|
|
|
|
Indexing and Performance