dhechle (4/30/2014)

---

I have always believed best practice when writing stored procedures or any SQL code is to include error handling. I was challenged today though as to why include error handling in a certain ETL project being written at the moment, I think its quite obvious that if there is some sort of failure then the load should roll back instead of leaving it in a non consistent state.

I was then asked as to what scenarios might a failure occur, there is the obvious of network blips, servers failing, databases failing, deadlocks occurring, table being accidentally dropped, can you think of any specific reasons as to why you have used error handling in any projects and when it has provided useful.

thanks in advance.