This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

AnnouncementAnnouncement Module

Collapse

No announcement yet.

SqlServerMaxValueIncrementer getNextKey method and the delete statementPage Title Module

As far as I can tell, the getNextKey method is performing the following:
1. insert a row into table so the identity column generates the next key value
2. select identity column value from table
3. Delete the rows from table except last row

I ask this because I occasionally see SQLServer deadlocks caused by the delete SQL statement when multiple jobs are running (not launched at the same time but are accessing the BATCH_STEP_EXECUTION_SEQ table roughly at the same time).