Background info - I have a table that stores Job information with a unique
JobID (PK) and a
ClientID (one client can have many jobs), as well as bunch of columns that are heaped data.
I have ran
sp_BlitzIndex and it returned this:
dbo.Job.PK_Job_1 (1): Row lock waits: 399; total duration: 21 minutes; avg duration: 3 seconds; Page lock waits: 171; total duration: 2 minutes; avg duration: 1 seconds; Lock escalation attempts: 125,805; Actual Escalations: 0.
This table only has 35K rows in it, but it is heavily used and updated every few seconds. The current index is on the PK which is a unique value. I do not know much about index tuning, but if I remove this index and create a nonclustered index for the
JobID + ClientID, am I on the right track to reducing the aggressiveness of the index? Or am I making it worse?