August 25, 2009 at 6:28 pm
I am replaying profiler trace on other server and have couple of issues
1) I am not able to map which event created error as it shows error in
replay as not able to replay but not the actual event as replay the original
trace reaches to the botton, any soln to that?
2) when i import the eventclass to table it shows ids so not able to select
only the errors one
thanks for your time!!
August 26, 2009 at 9:06 am
sqlquery (8/25/2009)
I am replaying profiler trace on other server and have couple of issues1) I am not able to map which event created error as it shows error in
replay as not able to replay but not the actual event as replay the original
trace reaches to the botton, any soln to that?
2) when i import the eventclass to table it shows ids so not able to select
only the errors one
thanks for your time!!
1. I'm not sure what you mean here. But I think the issue is related to the trace not replaying against the correct database. Here's some information directly from the BOL entry, Replay Requirements
To replay a trace against a server (the target) on which SQL Server is running other than the server originally traced (the source), make sure the following has been done:
All logins and users contained in the trace must be created already on the target and in the same database as the source.
All logins and users in the target must have the same permissions they had in the source.
All login passwords must be the same as those of the user that executes the replay.
The database IDs on the target ideally should be the same as those on the source. However, if they are not the same, matching can be performed based on DatabaseName if it is present in the trace.
The default database for each login contained in the trace must be set (on the target) to the respective target database of the login. For example, the trace to be replayed contains activity for the login, Fred, in the database Fred_Db on the source. Therefore, on the target, the default database for the login, Fred, must be set to the database that matches Fred_Db (even if the database name is different). To set the default database of the login, use the sp_defaultdb system stored procedure.
Replaying events associated with missing or incorrect logins results in replay errors, but the replay operation continues.
2. Yes, when saving trace results to a table the eventclass only saves the id. The mapping to the name happens in the profiler gui. You can get the Name by joining to sys.trace_events. Here's a link[/url] to a script that gives you an idea of how to do it. You just need to replace sys.traces with fn_trace_gettable().
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
August 26, 2009 at 9:30 am
The Ids which were there in the source system should be readily available in the destinatio server.
Thanks.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply