May 3, 2010 at 12:36 pm
A dev just came by my cube to ask if there was anything wrong with the DB.
He is getting duplicate inserts and syas no code has changed.
Are there some specific checks I can run to verifiy DB is in good shape? ie ddcc checkdb.
This DB is in production..so I must tread lightly.
May 3, 2010 at 12:48 pm
It's most likely the problem is in the code, not the database.
>>>"He is getting duplicate inserts"
What exactly does that mean?
May 3, 2010 at 12:51 pm
Agreed.
Just looking for some outputs to prove DB is in good order....ie dbcc check db...or something similar...but that I can run on a prod box
May 3, 2010 at 1:42 pm
You can run a checkDB, but corruption won't cause duplicate inserts. It causes high severity error messages.
Run profiler (or a server-side trace) to see what's happening to the database if you need proof, but this is a code problem, not a database problem. SQL doesn't just run inserts twice for fun.
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
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply