sql server - Perfomance Issuses on Tables With NonClustered Index -
We have a table with nearly 100,000 records that are often used in our applications. We had an identity column and had a package index on it and used to do everything well, but for some reasons we had to use a unique identity column as the primary key. So we add a non-cluster based index to it and remove the package indicator on the id column. But now, there are lots of performance degradation in our time from our customers, is it because the table no longer has a package index?
This means that you had to leave the package index, two concepts are different. You have a unique identifier, Can be implemented by non-indexed indices and different package indexes of elections (such as old But the real question is, when you add a unique identifier, PK how did you change your application? Have you modified the application code to get the record through this new PK (Unique Identifier)? Have you included everyone in the context of the new PK? Have you modified all foreign key cosntraints which refers to the old Ultimately you have a problem solving problem and see it as a performance troubleshooting problem. I have two great resources for you: and id columns).
id column? Or does the application continue to retrieve data using the old identity,
id column? My expectation is that you have changed both into applications and table, and now there is a table in the table with "SELECT ..." table WHERE pk = @ uniqueidentifier As is now prevalent. If such access is reached, only , then the table should not be corrected with a non-clustered unique identifier primary key and a package index. Therefore, there should be something else on play:
column
id column
Comments
Post a Comment