April 19, 2018 at 3:11 pm
Hi - Captured the trace from source server and ran them in destination. Question, how to compare the results to do the query level benchmarking now? Please advise
Thanks.
April 20, 2018 at 10:29 am
SQL-DBA-01 - Thursday, April 19, 2018 3:11 PMHi - Captured the trace from source server and ran them in destination. Question, how to compare the results to do the query level benchmarking now? Please advise
Not sure exactly what you mean... Are you talking about taking a trace of a query and then re-playing that same trace on a different server, or are you trying to re-create the same trace on a different server? Or are you looking to figure out how to compare the results of the same trace taken on two different servers? You mention both benchmarking (in the post) and re-play (in the title), so I'm not quite sure what the objective is...
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
April 20, 2018 at 10:42 am
Compare the results of the same trace taken on two different servers
Thanks.
April 20, 2018 at 10:51 am
SQL-DBA-01 - Friday, April 20, 2018 10:42 AMCompare the results of the same trace taken on two different servers
Okay, cool. Easiest way to do this: Save the results of the trace to a table on both servers. Then you just compare the data in the tables... Alternatively, you have two RDP sessions, one to view each trace, and you see them side by side... So perhaps it depends on what needs to be compared... That's why saving the results to a table is the best way to go. That way you can worry about what to keep AFTER the trace is taken,
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
April 20, 2018 at 10:56 am
How to find the time elapsed to run a query in source server? The diff of start time and end time column does not provide proper elapsed time.
Thanks.
April 20, 2018 at 11:04 am
SQL-DBA-01 - Friday, April 20, 2018 10:56 AMHow to find the time elapsed to run a query in source server? The diff of start time and end time column does not provide proper elapsed time.
Which events are you looking at? Is there a stored procedure involved?
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
April 20, 2018 at 11:42 am
sgmunson - Friday, April 20, 2018 11:04 AMSQL-DBA-01 - Friday, April 20, 2018 10:56 AMHow to find the time elapsed to run a query in source server? The diff of start time and end time column does not provide proper elapsed time.Which events are you looking at? Is there a stored procedure involved?
Yes, prcs with parameters
Thanks.
April 20, 2018 at 1:34 pm
SQL-DBA-01 - Friday, April 20, 2018 11:42 AMsgmunson - Friday, April 20, 2018 11:04 AMSQL-DBA-01 - Friday, April 20, 2018 10:56 AMHow to find the time elapsed to run a query in source server? The diff of start time and end time column does not provide proper elapsed time.Which events are you looking at? Is there a stored procedure involved?
Yes, prcs with parameters
Ummm... not sure what you mean by "prcs". I'm referring to the list of events and the columns within those events that you have checked off to run the trace against. Profiler can often obscure performance numbers because it can at times impose a burden significant enough to skew the results, especially for shorter duration queries, and in cases with any significant re-compiles going on. How long does the stored proc run, roughly? Are you asking Profiler to provide an execution plan for each query? That can really mess up duration. Also, if some of your sproc runs real fast, you might need to enable the option to measue time in microseconds instead of milliseconds.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply