Tom Collins wants to know what’s going wrong:
We have an ETL job failing every night . The ETL job is using SQL Server Stored Procedures , so we’re looking to be trace the errors reported in SQL Server, to give some clues on how to fix the problem?
Do you have an approach to monitor and save SQL Server error messages ?
This is an extremely useful way of catching problems in code, as well as people goofing up ad hoc queries.