| Author |
Read80Trace.exe in SQL Server 2005
|
|
| baddy 2006-02-10, 11:23 am |
| My present production environment is in SQL Server 2000 and we are
planning to upgrade to SQL Server 2005 soon. I use the profiler a lot
and then use Read80trace.exe to process the trace files.
However, the Read80Teace does not accept a trace file from SQL Server
2005 and a SQL Server 2000 profiler does not connect to SQL Server
2005.
Are there any other tools similar to Read80Trace.exe for SQL Server
2005? If not, is there a way to trick the tool to accept a file from
SQL server 2005?
Thanks.
| |
| pasilveira@gmail.com 2006-02-14, 1:23 pm |
| Sorry that I can't answer your question but I was hoping to get some help from you. :) I am interested in using Read80Trace.exe but have some questions on it. What specific eventclasses do you use when capturing your profile for use with Read80Trace? t
he documentation talks about capturing different events for different needs but is unclear as to what exactly is needed for use as a "minimul set". I would like to use the capture for reporting but do not need all of the events because I am not going to
use the Ostress tool. I just want the minimul set of events to get the most out of reporting... Any help you could offer would be greatly appreciated...
********************
********************
********************
**********
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
| |
| John Bell 2006-02-17, 11:23 am |
| Hi
The format of trace files seems to be different to SQL 2000, but you can
work around this by loading the SQL 2005 trace into a table and then
exporting it back into SQL 2000. You can then use SQL 2000 profile to read
the table and save it as a trace file to feed into Read80Trace.
John
"baddy" wrote:
> My present production environment is in SQL Server 2000 and we are
> planning to upgrade to SQL Server 2005 soon. I use the profiler a lot
> and then use Read80trace.exe to process the trace files.
> However, the Read80Teace does not accept a trace file from SQL Server
> 2005 and a SQL Server 2000 profiler does not connect to SQL Server
> 2005.
>
> Are there any other tools similar to Read80Trace.exe for SQL Server
> 2005? If not, is there a way to trick the tool to accept a file from
> SQL server 2005?
> Thanks.
>
>
| |
| John Bell 2006-02-17, 11:23 am |
| Hi
The event classes for Read80Trace are listed in the help file as
· SQL: Cursor Open/Close – Cursors
· Attention - Errors and warnings
· Audit:Login/Logout - Security Audit
· ExistingConnectio
n - Sessions
· RPC:Starting/Completed - Stored Procedures
· RPC:OutputParamet
er - Stored Procedures
· Prepare/Unprepare SQL - TSQL
· SQL:BatchStarting
/Completed – TSQL
If you use the scripted trace in the help file then it seems to log
everything, therefore if you want to script the trace I would create your own
by setting up the events above and using the file/script trace option in SQL
Profiler. These are the events for capture
For aggregation analysis check out the events described in the Events &
Columns for Aggregation in the Design Overview. This lists
· Audit:Login/Logout - Security Audit
· ExistingConnectio
n - Sessions
· RPC:Starting/Completed - Stored Procedures
· SP:Starting/Completed - Stored Procedures
It does not list the following, but if you are not using stored procedures
you may want to also capture (I have not seen if these are used in the
analysis)
· SQL:BatchStarting
/BatchCompleted – TSQL
· SQL:StmtStarting/StmtCompleted – TSQL
John
"Paul S" wrote:
> Sorry that I can't answer your question but I was hoping to get some help from you. :) I am interested in using Read80Trace.exe but have some questions on it. What specific eventclasses do you use when capturing your profile for use with Read80Trace?
the documentation talks about capturing different events for different needs but is unclear as to what exactly is needed for use as a "minimul set". I would like to use the capture for reporting but do not need all of the events because I am not going t
o use the Ostress tool. I just want the minimul set of events to get the most out of reporting... Any help you could offer would be greatly appreciated...
>
> ********************
********************
********************
**********
> Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
> Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
>
| |
| John Bell 2006-02-17, 11:23 am |
| Something else...
I had issues with transfering the columns of image datatype, so don't
capture BinaryData and LoginSID.
John
"John Bell" wrote:
[color=darkred]
> Hi
>
> The event classes for Read80Trace are listed in the help file as
>
> · SQL: Cursor Open/Close – Cursors
> · Attention - Errors and warnings
> · Audit:Login/Logout - Security Audit
> · ExistingConnectio
n - Sessions
> · RPC:Starting/Completed - Stored Procedures
> · RPC:OutputParamet
er - Stored Procedures
> · Prepare/Unprepare SQL - TSQL
> · SQL:BatchStarting
/Completed – TSQL
>
> If you use the scripted trace in the help file then it seems to log
> everything, therefore if you want to script the trace I would create your own
> by setting up the events above and using the file/script trace option in SQL
> Profiler. These are the events for capture
>
> For aggregation analysis check out the events described in the Events &
> Columns for Aggregation in the Design Overview. This lists
>
> · Audit:Login/Logout - Security Audit
> · ExistingConnectio
n - Sessions
> · RPC:Starting/Completed - Stored Procedures
> · SP:Starting/Completed - Stored Procedures
>
> It does not list the following, but if you are not using stored procedures
> you may want to also capture (I have not seen if these are used in the
> analysis)
>
> · SQL:BatchStarting
/BatchCompleted – TSQL
> · SQL:StmtStarting/StmtCompleted – TSQL
>
> John
>
> "Paul S" wrote:
>
? the documentation talks about capturing different events for different needs but is unclear as to what exactly is needed for use as a "minimul set". I would like to use the capture for reporting but do not need all of the events because I am not going
to use the Ostress tool. I just want the minimul set of events to get the most out of reporting... Any help you could offer would be greatly appreciated...[color=darkred]
| |
| John Bell 2006-02-17, 11:23 am |
| Opps.. this was supposed to be on my reply to baddy's post!!!
"John Bell" wrote:
[color=darkred]
> Something else...
>
> I had issues with transfering the columns of image datatype, so don't
> capture BinaryData and LoginSID.
>
> John
>
> "John Bell" wrote:
>
ce? the documentation talks about capturing different events for different needs but is unclear as to what exactly is needed for use as a "minimul set". I would like to use the capture for reporting but do not need all of the events because I am not goi
ng to use the Ostress tool. I just want the minimul set of events to get the most out of reporting... Any help you could offer would be greatly appreciated...[color=darkred]
| |
|
| I used to do that (manually load trace files into SQL tables) before
Microsoft opened up Read80Trace to the whole world. Read80Trace is
very very fast in loading a trace file into tables. For example, it can
load a 750 MB trace file (approximatelt 3.5 million rows in the trace)
and generate an RML output in about 2 minutes or less.
Nothing else that I know of comes anywhere close to this.
John Bell wrote:
> Hi
>
> The format of trace files seems to be different to SQL 2000, but you can
> work around this by loading the SQL 2005 trace into a table and then
> exporting it back into SQL 2000. You can then use SQL 2000 profile to read
> the table and save it as a trace file to feed into Read80Trace.
>
> John
>
| |
|
| I used to do that (manually load trace files into SQL tables) before
Microsoft opened up Read80Trace to the whole world. Read80Trace is
very very fast in loading a trace file into tables. For example, it can
load a 750 MB trace file (approximatelt 3.5 million rows in the trace)
and generate an RML output in about 2 minutes or less.
Nothing else that I know of comes anywhere close to this.
John Bell wrote:
> Hi
>
> The format of trace files seems to be different to SQL 2000, but you can
> work around this by loading the SQL 2005 trace into a table and then
> exporting it back into SQL 2000. You can then use SQL 2000 profile to read
> the table and save it as a trace file to feed into Read80Trace.
>
> John
>
| |
|
| it depends on what exactly you are trying to analyze. most imortant
you should include endtime column. with that info, you do not need the
start event. let me know if you need more specific info on what events
/ col to use.
| |
| John Bell 2006-02-18, 3:23 am |
| But did you use that technique to convert between the SQL 2005 trace files
and SQL 2000?
John
"baddy" wrote:
> I used to do that (manually load trace files into SQL tables) before
> Microsoft opened up Read80Trace to the whole world. Read80Trace is
> very very fast in loading a trace file into tables. For example, it can
> load a 750 MB trace file (approximatelt 3.5 million rows in the trace)
> and generate an RML output in about 2 minutes or less.
>
> Nothing else that I know of comes anywhere close to this.
>
>
> John Bell wrote:
>
>
| |
| baddy 2006-02-18, 11:23 am |
| I have saved a trace file into a trace table for analysis, but have not
tried saving a 2005 trace file in to a table and then importing it into
a 2000 trace for use by Read80Trace.
John Bell wrote:[color=darkred
]
> But did you use that technique to convert between the SQL 2005 trace files
> and SQL 2000?
>
> John
>
> "baddy" wrote:
>
|
|
|
|