Turning on Verbose logging in SQL Agent


When any critical error / warning is reported by SQL Server Agent, it is written to a log file MSSQL\Log\SQLAgent.out.  By default only critical errors and warnings are reported to this log file. If you would like to see additional information messages, here are the steps you could follow to enable verbose tracing

1) Launch Agent Properties dialog



2) Turn on “Include execution trace messages”; Click Ok



3) Restart  SQL Agent and View Current Agent Error Log






If you no longer need verbose turning you can turn off this option. When you see any errors in SQL Agent that is harder to trouble shoot, please turn on this option and report this log file to http://connect.microsoft.com . Detailed verbose logs would be useful for our development team during bug investigation process.

This posting is provided "AS IS" with no warranties, and confers no rights. 
Use of included script samples are subject to the terms specified at

Comments (1)

  1. HELP - I need SQL Server JOBS to print ALL Print statements says:

    I have SQL Scripts, encapsulated in SQLConcat. Developers need to see ALL the SQL PRINT output from their SQL scripts, but when I run them in JOBS, only 16 lines of print statements get written to my output file. Is there a way to GET ALL OUTPUT PRINT statements to write out to file?


    Richard Peninger

Skip to main content