Why has my Ticket ID jumped by 1000 tickets for no reason?

[Paul Betteridge]

This is rare but is not a CRS bug but a SQL Server bug/annoyance! This can happen when your SQL Server restarts or you reboot your SQL server machine (starting and stopping the SQL Server service). CRS Ticket IDs are unique based on the auto-incrementing index in the ticket database which is automatically incremented by SQL Server when a new ticket is created and inserted into the database. When SQL Server restarts, this can sometimes causes the IDs to cache and the next ticket gets a value larger than the last ID (typically 900-1000 IDs more which is a cache value used within SQL Server). CRS will be updated in the future to prevent this from happening (this is a big internal change which is why it is not done yet!).

[Author]

Posts