130 likes | 248 Views
5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR. Presented by : Sifiso Ndlovu. 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR. Less Lines Accurate Troubleshooting by Error Line Number
E N D
5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR Presented by: Sifiso Ndlovu
5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR • Less Lines • Accurate Troubleshooting by Error Line Number • Accurate Troubleshooting by Error Number • Accurate Termination of T-SQL Statement • Practice Statement Termination before learning to THROW
1. Less Lines RAISERROR THROW
2. Accurate Troubleshooting by Error Line Number RAISERROR THROW
3. Accurate Troubleshooting by Error Number RAISERROR THROW
5. Practice Statement Termination before learning to THROW RAISERROR THROW
5. Practice Statement Termination before learning to THROW THROW
5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR • Less Lines • Accurate Troubleshooting by Error Line Number • Accurate Troubleshooting by Error Number • Accurate Termination of T-SQL Statement • Practice Statement Termination before learning to THROW