November 7, 2017 at 4:21 pm
Hi all,
If I read the MS docu correctly I can't replay a trace defined on 2012, against a 2016 instance - is this correct???!??!
If so this would seem to be a huge flaw as how can your replicate a workload without running production scripts manually??
Thanks
JB
November 7, 2017 at 6:00 pm
I've replayed many 2008 traces (taken with the "T-SQL Replay" template) on 2016, using both Profiler and Distributed Replay.
To which doc are you referring?
Eddie Wuerch
MCM: SQL
November 8, 2017 at 4:03 am
Yeah, I'm with Eddie. I've done this in the past. It's just about capturing the correct events and then Distributed Replay just works. I freely admit I haven't used this facility in Trace for a number of years.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
November 8, 2017 at 4:54 am
I think you'll only get problems if your code uses features that are deprecated in the source version of SQL and have been discontinued in the version on the target server - fortunately, there don't appear to be any mentioned in the SQL Server Discontinued Functionality list that would apply in your situation (capturing 2014 to replay against 2016).
However, capturing from older SQL Server versions could cause problems. For example, code written to run against SQL Server 2008 could still use the old JOIN syntax (*=), and that would be captured in a trace; however, if you replayed that against a newer version of SQL Server, then that code would fail.
Thomas Rushton
blog: https://thelonedba.wordpress.com
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply