locked
Database Tuning Advisor can't read trace file. RRS feed

  • Question

  • I'm having the same issue documented in this thread:
    http://blogs.msdn.com/crm/archive/2007/08/13/using-database-tuning-advisor-with-
    crm.aspx


    I'm running 2005 SP2 and I still receive the error
    99% of consumed workload has syntax errors has syntax errors.
    How can I get DTA to actually do something on my tracefile?
    The blow references a script that will change the trace file to
    a different format and also mentions that SP2 fixes this issue.
    I have SP2 and the issue still occurs.
    Also isn't changing the input from parametized queries to hard values
    have the possibility of changing the explain plans? I know it does in
    DB2 and Oracle.

    Can somebody provide the script referenced in the blog above (it isn't posted where
    it is referenced to be posted) or suggest another solution.
    If this isn't appropriate for this blog, can someone document the sql server blog?

    Thank you.


    Here's an example of a standard trace file I collected with Sql Profiler. The example is 2 lines of a 500000 row trace file.

    SQL:BatchStarting    create proc #jtds000055  as UPDATE DMActivityLogStrng SET criteriaString = 'Importing Journal Completed data set: journal.lineitemlocation' WHERE activityLogId = 14 AND stringTypeId = 57    jTDS        gold                    123    53    2008-06-04 22:07:28.920           
    SQL:BatchCompleted    create proc #jtds000055  as UPDATE DMActivityLogStrng SET criteriaString = 'Importing Journal Completed data set: journal.lineitemlocation' WHERE activityLogId = 14 AND stringTypeId = 57    jTDS        gold    0    26    0    0    123    53    2008-06-04 22:07:28.920    2008-06-04 22:07:28.920       
    RPC:Completed    exec #jtds000055     jTDS        gold    0    14    1    3    123    53    2008-06-04 22:07:28.920    2008-06-04 22:07:28.920    0X0000000001000000160023006A007400640073003000300030003000350035001400000003000600380469006E00740000000000   

    Thursday, June 5, 2008 2:38 PM

Answers

  • I would recommend that you post your question to the SQL Server newsgroup, since it involves SQL Database Tuning Advisor
    --http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.server

    Sunday, June 8, 2008 11:26 PM
    Moderator

All replies