Advanced Error Tracking Get to the root issue immediately! MATT MARTIN SQL Saturday Atlanta | 2016

About 8 years working with SQL Server and SSIS Senior Manager at Fortune 50 Company Responsible for centralizing and building out data warehouse for .COM business Built financial forecasting and budgeting models for really big data sets MD Data Technologies Chief Technology Officer Twitter: @MDDataTech Website: www.sqletl.com Email: matt@sqletl.com

Agenda Common Error Tracking Options Another Creative Solution Identify bottlenecks in procs Where things went wrong Building an error and logging notification system to give you immediate feedback on SQL errors DEMO

Common Error Tracking Options Job Agent msdb.dbo.sysjobhistory table trigger Third Party Software Manual highlighting of lines of code and running one-by-one NOOOOOOOOO!!!!! A well formatted error tracking email with user feedback messages as they occur in the procedure Another Creative Solution

Identify bottlenecks in procs Most developers use a PRINT statement after each line of code. What’s wrong with PRINT? No immediate feedback. Don’t show up to the client until the proc finishes or SQL flushes the buffer

Identify bottlenecks in procs There is a way though to get REAL-TIME feedback! Answer: RAISERROR What? I don’t want to raise errors on my server! RAISERROR can be used to send back real-time messages to the client without having SQL Server throw an actual error by specifying a zero severity. RAISERROR('DATASET ISOLATED TO TEMP TABLE',0,1) WITH NOWAIT

How do we identify the bottleneck? The key is the “NOWAIT” part. This instructs SQL Server to output the message immediately. RAISERROR('DATASET ISOLATED TO TEMP TABLE',0,1) WITH NOWAIT This allows for real-time feedback and the developer does not have to wait until the end of the proc to see output statements.

Where things went wrong Utilizing a wrapper proc that integrates with Database Mail will generate a well formatted and professional email message.

Where things went wrong Place your existing proc in a try/catch CREATE PROC usp_my_proc AS SET NOCOUNT ON; BEGIN TRY EXEC usp_feedback 'attempt to divide by zero' SELECT 1/0 END TRY BEGIN CATCH DECLARE @db_nm varchar(250) = db_name() EXEC usp_etl_err_log @@procid, @db_nm, 'my custom message' END CATCH Just call usp_etl_err_log and the email will go

Now the Fun Stuff! DEMO Building an advanced error notification system