Hi,
We have a highly concurrent system (~20-30 concurrent requests) which basically does heavy INSERT & UPDATES on few (3 to 4 )tables.
all these tables have IDENTITY columns which is PK for that table too.
We observe performance hit in our long running tests, where system just doesn't respond.
I see there is enough RAM and CPU on the server but too many commands in SUSPENDED state for PAGELATCH_*
IS it bad practice to have IDENTITY in such scenario?
Please guide me.
Thanks in advance!!
We have a highly concurrent system (~20-30 concurrent requests) which basically does heavy INSERT & UPDATES on few (3 to 4 )tables.
all these tables have IDENTITY columns which is PK for that table too.
We observe performance hit in our long running tests, where system just doesn't respond.
I see there is enough RAM and CPU on the server but too many commands in SUSPENDED state for PAGELATCH_*
IS it bad practice to have IDENTITY in such scenario?
Please guide me.
Thanks in advance!!