We're running a 3rd party ASP application with SQL 2008 Web edition. I suspect the application is failing to record some transactions and isn't reporting SQL errors, e.g., timeouts. I've confirmed with the vendor that the application does not report or log errors in any way.
I'd like to not have to instrument the application code and am looking for another solution to identify any SQL errors that may be happening.
Is there any such tool available or is this built into SSMS?
PS: I am a casual user of SQL these days but when pointed in the right direction, I usually get there.
I think you could trap those with SQL Profiler - which can "spy" on all SQL statements sent to the server. There might also be some system views that will yield that information, which would be easier to report on (compared to using SQL Profiler), but SQL Profiler would get you going in a simple fashion - the difficulty might be separating the Wheat from the Chaff.
I'd give the vendor a good kicking too - how are they ever going to provide support and diagnose a problem if they don't have any means of diagnosing it?
And just to clear this up... you do need to post X messages. We had a similar thing on the old site that I hacked together. I've been manually upgrading people from the old forums as I find them.