![Page 1: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/1.jpg)
5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of
RAISERROR
Presented by: Sifiso Ndlovu
![Page 2: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/2.jpg)
5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR
1. Less Lines2. Accurate Troubleshooting by Error Line
Number3. Accurate Troubleshooting by Error
Number4. Accurate Termination of T-SQL Statement5. Practice Statement Termination before
learning to THROW
![Page 3: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/3.jpg)
1. Less LinesRAISERROR
THROW
![Page 4: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/4.jpg)
2. Accurate Troubleshooting by Error Line Number
RAISERROR
THROW
![Page 5: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/5.jpg)
3. Accurate Troubleshooting by Error Number
![Page 6: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/6.jpg)
3. Accurate Troubleshooting by Error Number
RAISERROR
THROW
![Page 7: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/7.jpg)
4. Accurate Termination of T-SQL Statement
RAISERROR
![Page 8: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/8.jpg)
4. Accurate Termination of T-SQL Statement
THROW
![Page 9: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/9.jpg)
5. Practice Statement Termination before learning to THROW
RAISERROR
THROW
![Page 10: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/10.jpg)
5. Practice Statement Termination before learning to THROW
THROW
![Page 11: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/11.jpg)
5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR
1. Less Lines2. Accurate Troubleshooting by Error Line
Number3. Accurate Troubleshooting by Error
Number4. Accurate Termination of T-SQL Statement5. Practice Statement Termination before
learning to THROW
![Page 12: 5 Reasons You Should Handle SQL Server Exceptions Using THROW Instead of RAISERROR](https://reader036.vdocuments.us/reader036/viewer/2022062501/56816223550346895dd251e9/html5/thumbnails/12.jpg)
Questions…