none
Rendering verbose the SQL Server error log - SQL Server 2008 R2/2012

    Question

  • Hi,

    is it possible to render verbose the SQL Server error logs?

    Could a such operation affect the performance of the SQL engine?

    Thanks

    Sunday, October 20, 2013 6:39 AM

Answers

  • As I already replied in an earlier post: No, there's no such general setting. 

    If you want more, then you need to be specific so we can look for a more "customized" solution. There's no "verbose" setting for the errorlog file.


    Tibor Karaszi, SQL Server MVP | web | blog

    Monday, October 28, 2013 10:05 AM
    Moderator

All replies

  • Yes you can set the logging.<o:p></o:p>

    Can follow below link for this:<o:p></o:p>

    http://blogs.msdn.com/b/sqlagent/archive/2010/10/15/turning-on-verbose-logging-in-sql-agent.aspx<o:p></o:p>

    It is not advisable to run this all time on production server as it hits the performance due to trace run.

    Use this option only if you are facing some issue to capture the facts.


    Please click the Mark as answer button and vote as helpful if this reply solves your problem

    Monday, October 21, 2013 4:42 AM
  • Ok, but I'm not talking about the SQL Server Agent error log.

    Thanks

    Monday, October 21, 2013 7:35 AM
  • Hi pscorca,

    Usually, you can check or view the SQL Server error log by using SQL Server Management Studio or any text editor. By default, the error log is located at Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG. Or you can refer to the following steps for viewing the error log.

    1.In Object Explorer, expand a server, expand Management, and then expand SQL Server Logs.

    2.Right-click a log and click View SQL Server Log.

    However, if you want to use extended events or SQL Trace to capture the error log for troubleshooting problems, it will affect the performance of SQL. If you just read the error log via SQL Server Management Studio or text editor. Personally It will not affect the performance of the SQL .

    Thanks,
    Sofiya Li


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Friday, October 25, 2013 9:20 AM
    Moderator
  • There's no such setting like "verbose" for the db engine errorlog file. Can you clarify what your situation is, and what it is you want to achieve?

    Tibor Karaszi, SQL Server MVP | web | blog

    Saturday, October 26, 2013 3:54 PM
    Moderator
  • Hi,

    is it possible to render verbose the SQL Server error logs?

    Could a such operation affect the performance of the SQL engine?

    Thanks


    if you can provide more information then we can provide more info

    Thanks, Rama Udaya.K (http://rama38udaya.wordpress.com) ---------------------------------------- Please remember to mark the replies as answers if they help and UN-mark them if they provide no help,Vote if they gives you information.

    Saturday, October 26, 2013 7:47 PM
  • About rendering verbose the SQL Server error log I intend to do to capture major details for a possible error, fe a deadlock. But I prefer to think a generic error and not only to a specific one.

    Thanks

    Sunday, October 27, 2013 6:59 PM
  • About rendering verbose the SQL Server error log I intend to do to capture major details for a possible error, fe a deadlock. But I prefer to think a generic error and not only to a specific one.

    Hi pscorca,

    According to your description, if you want to capture major details for a deadlock error . I recommend you can use SQL Server Extended events to monitor deadlock, or you can enable trace flags, such as Trace Flag 1204 or 1222, or you can run SQL Profiler trace to capture the deadlock events.

    For more information, you can review the following blog about how to monitor deadlock.
    http://blogs.msdn.com/b/sqlserverfaq/archive/2013/04/27/an-in-depth-look-at-sql-server-memory-part-2.aspx

    Thanks,
    Sofiya Li


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Monday, October 28, 2013 1:38 AM
    Moderator
  • Capturing deadlock is an example.

    Is it possible or not to render verbose the SQL Server error log in order to capture in general maior details about an error?

    Thanks

    Monday, October 28, 2013 7:31 AM
  • As Sofiya said to capture those information you can enable the trace flags so those will log when deadlock victim happens, see the following all information gives how to analyze

    Also in  SQL  server 2005 and 2008, you also have option called- run a trace to capture deadlock info in the XML so that you can capture & analyze.

     Deadlock Troubleshooting, Part 1
    http://blogs.msdn.com/b/bartd/archive/2006/09/09/deadlock-troubleshooting_2c00_-part-1.aspx

    Analyze Deadlocks with SQL Server Profiler
    http://support.microsoft.com/kb/169960/en-us

    Analyze Deadlocks with SQL Server Profiler
    http://technet.microsoft.com/en-us/library/ms188246.aspx

    How to monitor deadlock using extended events in SQL Server 2008 and later
    http://blogs.msdn.com/b/sqlserverfaq/archive/2013/04/27/an-in-depth-look-at-sql-server-memory-part-2.aspx


    Thanks, Rama Udaya.K (http://rama38udaya.wordpress.com) ---------------------------------------- Please remember to mark the replies as answers if they help and UN-mark them if they provide no help,Vote if they gives you information.

    Monday, October 28, 2013 8:41 AM
  • As I already replied in an earlier post: No, there's no such general setting. 

    If you want more, then you need to be specific so we can look for a more "customized" solution. There's no "verbose" setting for the errorlog file.


    Tibor Karaszi, SQL Server MVP | web | blog

    Monday, October 28, 2013 10:05 AM
    Moderator