SQL Server Performance

profiler help

Discussion in 'Performance Tuning for DBAs' started by lara99, Nov 21, 2007.

  1. lara99 New Member

    Hi, guys I want to run profiler trace on my production. to get the long running queries
    and the index usage,I wan to use trace file as the input to ITW as workload file.
    Here I am in doubt whether to run the trace for each individual
    database by filtering the trace by database id, or run the whole trace and
    while running ITW use different databases with same workload file. Please suggest.
    I hope I explained my situation clearly.
    Thanks .
  2. Greg Larsen New Member

    Are you trying to tune just one application that uses one database. If so collect information only for that database. Now if you have an application that using multiple databases then collect stats for all databases used. Don't trace for any more than you need.
  3. Luis Martin Moderator

    You can run profiler for all databases.
    But, after your finished your trace, pick each long query, paste into Query Analyzer and run ITW. I don't recommend to run ITW on all trace.
  4. ranjitjain New Member

    As you will be tuning one db at a time or ITW on one DB at atime, so better keep the set of long queries group by Databases. So run your profiler to trace queries for single db at a time which will even give you counter of queries for specific db.

Share This Page