briancampbellmcad (12/8/2012)
Is this a sign of a corrupted database?
No.
This happened just after I manually deleted all records from a table and a few of them gave errors of something like "cannot delete" due to some type of unique key violation... I was able to eventually delete them all but this may have corrupted it?
Nope.
If the database is corrupt should I script out the entire database and recreate it?
Well, it's not a sign of corruption anyway, and scripting out a DB is not the way you recover from corruption.
It looks like either the trigger does more than one operation or the trigger's operations are firing other triggers or there's more than one trigger on the table.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability