How to Use a SQL Profiler template to capture Track-It! database information?

Version 4
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Track-It!


    COMPONENT:

    Track-It! 2020 R1


    APPLIES TO:

    All Track-It! Versions



    QUESTION:

    How to Use a SQL Profiler template to capture Track-It! database information?


    ANSWER:


     Determining the type of SQL Trace to be captured.
      1. SQL Profiler trace can capture detailed data and information during the execution of erroring or slow transactions.
      2. Traces can be cultured to capture different events and columns of data, depending upon the type of issues/errors.
      3. Issues and Errors that may require different Trace templates: Performance, Deadlock errors, individual erroring/slow queries, individual erroring/slow transactions, Erroring reports, erroring/slow Business Rules, delays or deadlock errors with Business Rules, others.
      4. SQL Server and Client install stock Trace templates at directory: <path>\Program Files\Microsoft SQL Server\80\Tools\Templates\SQL Profiler\.



    Processing/Capturing the SQL Profiler Trace.
    1. In SSMS click Tools -> SQL Server Profiler.
    2. Login as an SA user to the instance you are going to be monitoring. It doesn't have to be the local server.
    3. Under the General tab I like to select the 'TSQL' template but you don't have to.
    4. Under the Event Selections tab, enable both the 'Show all events' and 'Show all columns' options at the bottom.
    5. Under the Errors and Warnings event grouping, enable 'User Error Message'.
    6. Under the Security Audit grouping I usually turn off the 'Audit Login' and 'Audit Logout' options because it would just add more stuff to look at to the trace, which probably won't helpful.
    7. Under the Sessions grouping, I turn off the 'ExistingConnection' option. Again it would just add to the trace and probably wouldn't be helpful.
    8. Under the Stored Procedures grouping I like to enable these options:
    RPC:Starting
    SP:StmtStarting
    9. Under the TSQL grouping I like to enable these options:
    SQL:BatchStarting
    SQL:StmtStarting
    10. Next, click the Column Filters button in the lower right.
    11. Select DatabaseName and then expand 'Like' on the right side.
    12. Type in the name of the database you want to monitor specifically.
    13. Click OK to save the filter.
    NOTE: If the SQL server instance you are going to monitor only has 1 Track-It! database these last few steps really aren't necessary but it helps when you have several Track-It! databases on the same server that may end up polluting the trace.
    14. Click the Run button.
    15. Click the red Stop button at the top and don't start the trace until you are ready in Track-It! to take some action that you want to watch. This will help to keep the noise down in the trace.
    16. Save the Trace file as customer_sql_trace.trc.




     


    Article Number:

    000191366


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles