locked
Sql trace performance RRS feed

  • Question

  •  

     

    Hi all,

     

    As a developer I have worked with all the tools provided by Sql server package (from  the former 7 to the new 2005) and never felt that I shouldn´t use them  because of performance issues! Now my systems collegue says to me that running a sql trace is very bad for the database. I have checked and for me doesnt seem that way.. Is  this true? Running a trace can bring me a performance problem? When do you ususally use traces? 

     

    Thaks in advance for all the posts!

     

    BL

     

     

    Wednesday, December 26, 2007 10:00 AM

Answers

All replies

  • Yes , your colleague is true that SQL Server Trace /Profiler may overload your system. Generally, in production environment we run trace as last option. If its not a highly transactional or you have enough resources  you may not feel the performance degradation. 

     

    If you give proper column and event filter you can again fine tune your trace.

     

    Madhu

     

    Wednesday, December 26, 2007 10:34 AM
  • Well yes.. any tool that is connected to a server may overload a system , but to become a problem? How can I detect if is this the case?

     

    Thank you!

     

    BL 

     

    Wednesday, December 26, 2007 10:55 AM
  • A trace /profiler without proper filter can cause potential perf issue on a busy server. Each and ever event run on the system has to be logged and to be written into file or table.

     

    Check these threads

     

    http://sqlblog.com/blogs/linchi_shea/archive/2007/08/01/trace-profiler-test.aspx

    http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm

     

     

    Madhu

    Wednesday, December 26, 2007 11:07 AM