You must Sign In to post a response.
  • Category: SQL Server

    What is SQL Server Profiler?

    what is SQL Server Profiler ?
    what is its use ?
  • #600576
    Hi,

    SQL profile is used when you wanted to know what how SQL query is executing behind the server. It gives you complete details like, what query is executing, how much time it is taking etc. It is basically a monitoring tool, and it has got Graphical user interface. you just need to select the database you wanted to trace, profiler will do rest of the things for you.

    Refer MSDN article for detailed information,
    http://msdn.microsoft.com/en-us/library/ms187929.aspx


    Regards,
    Asheej T K

  • #600601
    SQL Server Profiler
    -------------------
    * Its a tool which is used to capture SQL Server events on the database server.
    * It will save the events in a trace file which can be used for the audit purpose.
    * It is mainly used for analyzing and debugging SQL stored procedures.

    All is well.
    Thanks,
    Dharma
    Editor,Mentor,MVM
    Try and fail but don't fail and try

  • #600679
    Hi,

    SQL Profiler is a tool,which is used to capture events from a server.These events are saved in a trace file that is referred to later to replay a specific series of steps when trying to diagnose a problem.SQL Profiler is used for the following activities.

    1> Stepping through problem queries to find the cause of the problem.

    2>Finding and diagnosing slow-running queries.

    3>Capture the series of SQL statements that lead to a problem.The saves trace can
    then be used to replicate the problem on a test server where the problem can be diagnosed.

    4>Monitoring the performance of SQL Server to tune workloads.

    SQL Profiler can be accesed from the Tools menu of SQL Enterprise Manager.


    Thanks & Regards


    Bunty

  • #600691
    According to my knowledge, I have configured SQL Server profiler to send a mail alerts. I have used this in the Package to send a mail from the DB.
    Regards,
    Manick

  • #600788
    Using SQL Server Profiler

    SQL Server Profiler shows how SQL Server resolves queries internally. This allows administrators to see exactly what Transact-SQL statements or Multi-Dimensional Expressions are submitted to the server and how the server accesses the database or cube to return result sets.

    Using SQL Server Profiler, you can do the following:

    Create a trace that is based on a reusable template

    Watch the trace results as the trace runs

    Store the trace results in a table

    Start, stop, pause, and modify the trace results as necessary

    Replay the trace results

    Use SQL Server Profiler to monitor only the events in which you are interested. If traces are becoming too large, you can filter them based on the information you want, so that only a subset of the event data is collected. Monitoring too many events adds overhead to the server and the monitoring process, and can cause the trace file or trace table to grow very large, especially when the monitoring process takes place over a long period of time.


    link to refer: http://msdn.microsoft.com/en-us/library/ms187929.aspx

  • #601054
    SQL Server Profiler shows how SQL Server resolves queries internally. This allows administrators to see exactly what Transact-SQL statements or Multi-Dimensional Expressions are submitted to the server and how the server accesses the database or cube to return result sets.

    Using SQL Server Profiler, you can do the following:

    Create a trace that is based on a reusable template

    Watch the trace results as the trace runs

    Store the trace results in a table

    Start, stop, pause, and modify the trace results as necessary

    Replay the trace results

    Use SQL Server Profiler to monitor only the events in which you are interested. If traces are becoming too large, you can filter them based on the information you want, so that only a subset of the event data is collected. Monitoring too many events adds overhead to the server and the monitoring process, and can cause the trace file or trace table to grow very large, especially when the monitoring process takes place over a long period of time.


  • This thread is locked for new responses. Please post your comments and questions as a separate thread.
    If required, refer to the URL of this page in your new post.