A colleague of mine noticed incorrect ids generated for inserted items. Most probable cause: some script issues a command like the following:
dbcc checkident('dbo.table', reseed, 1)
I have thought about setting up a DDL trigger to catch this commands, but this list of DDL events does not seem to include anything related to reseeding.
Question: is there a way to catch such commands in a similar way DDL triggers catch various database schema changes?