Checking logs for missing records

  • We have an application that writes to the database, and we've come across a couple instances where individual records appear to be missing. For example, our WorkOrders table will contain records with ID's such as 300, 301, 302, 304 etc, and 303 will be missing. Since this field is an integer identity, the only thing I can think of is a transaction that was rolled back, but the associated records in other tables are stil present (cascading deletes are not set up, if that matters). Can this level of detail be captured by logging? The in-application logging that we have claims that the entry was made to the db, but I don't know how to verify that in Sql Server. Any suggestions would be appreciated.

  • If its an identity it can be missed by a rolled back transaction. If a transaction is begun, a record is written to the log, and then the transction is rolled back, the id will have been incremented, you lose that value. I don't know if that is your problem here but I know it is possible.

    CEWII

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply