Hi,
I have been working with SQL server for about 12 years now, but have never really kicked around trace flags - which I suspect this issue is associated with.
I have a number of very busy SQL servers but the only thing in the error log is the backup info (log and DB). I want to see all SQL errors (just found that an app was failing silently trying to add a duplicate key to a table, for example).
Do I have to turn on 3605, or another/combination of traces?
I know that there is a performance kicker, but the app developers are not, well, the BEST that ever graced our planet (being as polite as I can here...) and I need to monitor the error log.
Any help/advice appreciated
I have been working with SQL server for about 12 years now, but have never really kicked around trace flags - which I suspect this issue is associated with.
I have a number of very busy SQL servers but the only thing in the error log is the backup info (log and DB). I want to see all SQL errors (just found that an app was failing silently trying to add a duplicate key to a table, for example).
Do I have to turn on 3605, or another/combination of traces?
I know that there is a performance kicker, but the app developers are not, well, the BEST that ever graced our planet (being as polite as I can here...) and I need to monitor the error log.
Any help/advice appreciated