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 |
|
Lijo Cheeran Joseph
Posting Yak Master
123 Posts |
 Posted - 2010-11-25 : 03:21:50
|
| Hi Team,I am trying to tune a database, first time in my life. I have got a list of ‘costly indexes’. The costliest index is a clustered index which is on a primary key. The table structure is (ProcessStepID INT (PK), SubmissionReviewID INT, LKProcessStepCode VARCHAR(50))The ProcessStepID is the primary key. The SubmissionReviewID can be null (most of the time) when the record is created in this table. Then it will get updated.Is it a good idea to create a clustered index based on SubmissionReviewID (and then create primary key as ProcessStepID) ?Please advise…Note: High cost queries are found using: [Maintenance cost] = (user_updates + system_updates)ThanksLijo |
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2010-11-25 : 04:38:03
|
What do you mean by this: quote:
Note: High cost queries are found using:[Maintenance cost] = (user_updates + system_updates)
What are "user_updates" and "system_updates"?- LumbagoMy blog (yes, I have a blog now! just not that much content yet) -> www.thefirstsql.com |
 |
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2010-11-25 : 04:42:14
|
| http://www.simple-talk.com/sql/learn-sql-server/sql-server-index-basics/- LumbagoMy blog (yes, I have a blog now! just not that much content yet) -> www.thefirstsql.com |
|
|
|
|
|
|
Performance Tuning Scenario: Index question