Replay your workload as it is your actual one!
Download as PPTX, PDF0 likes1,248 views
The document discusses the Distributed Replay feature in SQL Server 2012, which allows users to replay workloads for application compatibility, performance testing, and forecasting. It outlines the components necessary for setting up the environment, including tools like the administration tool, controller, clients, and target server. The process involves capturing a workload, preprocessing it, selecting a replay mode, and analyzing the results, emphasizing the importance of documentation and community sharing.
Replay your workload as it is your actual one!
- 1. Replay your workload as it’s your actual one! Boris Hristov SQL Server DBA, Speaker, Trainer, Blogger
- 2. So who am I? @BorisHristov
- 3. How many of you…
- 4. reasons why
- 5. Possible scenarios: 1.Application compatibility 2.Performance / Load testing 3.Forecasting
- 6. What tools to use?
- 9. These are cool… … but not cool enough!
- 10. “There’s a new player in town!”DISTRIBUTED REPLAY
- 11. So what’s Distributed Replay? SQL Server 2012 feature Available in all editions (kind of…) Works with 2005 and higher (kind of…)
- 12. Distributed Replay Components 1. Administration tool – the cmd tool to manage the replay1. Administration tool – the cmd tool to manage the replay 2. DReplay Controller – the brain behind the replay 3. DReplay Client – machines(up to 16) that replay the workload 4. Target Server – The SQL Server instance you replay against
- 13. OK, but how are they working together?
- 14. DEMO Setting up DReplay Environment (installing gotchas)
- 15. Installation requirements and gotchas 1. Services must run under domain user accounts 2. Firewalls must allow the traffic of DR Components 3. DCOM permissions must be configured 4. SQL Server logins for the clients need to be created
- 16. So how do we issue a replay?
- 17. Step 1: Capture a trace!
- 18. Step 2: Preprocesses the .trc file/s
- 19. Step 3: Decide on replay mode and options
- 20. Step 4: Replay the preprocessed trace
- 22. Replay your workload. The steps. 1. Capture the workload with Profiler (TSQL-Replay) 2. Preprocess the trace with “dreplay preprocess” 3. Decide on a mode – synchronization or stress 4. Replay the workload with “dreplay replay” 5. Analyze the results
- 23. The GUI that is in beta from 2011
- 24. At the end 1. The Tool for replaying mission critical workloads 1. Don’t be afraid of not having a GUI 2. Capture -> Preprocess -> Replay 3. Document, blog, share it with the community!
- 25. Resources My blog – FAQ and RunAs Radio Podcast Channel 9 - Joe Sack(SQLSkills) Intro and Demo Jonathan Kehayias(SQLSkills) Intro and Demo Microsoft Peace of Mind Video MSDN Documentation Distributed Replay GUI (in beta) … you and me now
- 26. A big thanks to our sponsors
- 27. A big thanks to our sponsors
- 28. Thank you!
Editor's Notes
- #3: Senior DBA at HP Enterprise Services in Bulgaria, working for Fortune 500Regular speaker at conferences / webcasts / podcastsTrainer for external companiesTeacher at the 2 biggest universities in BulgariaVery active on twitter / blogging / hangoutsMore on LinkedInEasyest way to reach me – twitterA lot of SQL Server in my world
- #4: Have ever considered capturing and replaying their workload?How many of you have done that? Why, how is this helpful?
- #6: Application compatibility meaning both upgrade or migration of the app
- #7: The maestro!
- #8: The maestro! Debug!
- #9: -T enable trace flag -r number of iterations for each connection to execute its input file/query -p network packet size for connections - SQL Server only -n number of connections – multiplying the workloadProblems with SQL Server 2012 …
- #10: but you know the words – it’s not cool enoughSCALE is your word!
- #11: What is this doing actually? Few words about the functionality.
- #12: Thank god there is no support for SQL Server 2000 anymore…Developer – DR Controller allows just 1 clientCannot replay to an older version! 2005 -> 2008 2008 -> 2008 and higherWindows Server 2008 SP2 and higherDR Controller feauture - 160 MB DR Client - 1.9GBCan be installed via Parameters – DREPLAY_CTLR , DREPLAY_CLT, TOOLS
- #13: Administration tool – you have to install the Management Tools Complete
- #15: 1280 x 960 primaryWhy when you click just next next next it will not actually workDCOM -> Distributed Component Object Model – technology of microsoft for communication between software components across the network
- #18: More columns can be added, but will be removed in the preprocesses Replay Template is the minimum amount of eventsUSE SERVER-SIDE TRACE OF COURSE!
- #19: Sorts the events in ascending order based on EventSequenceRemoves all events and columns that are not replayableGenerates 2 files – (intermediate file) one xml and system fileGoal is to preprocess the trace once and replay it by using various optionsAnd you have the options to include / exclude the system sessions and to remove the idle time between the users events
- #20: Default – stressSync – replays the sequence of the whole trace – for high fidelity (correctnes) – functional testingStress – guarantees that the events will be ordered correctly per SPID or connectionIn stress you can use all options
- #21: CommunicatesDivides the workload per clientsDON’T FORGET the replay can be faster in the new environment – but the connection time and think time are controlling this!
- #22: Check the DR Controller configuration file -> set to syncCapture simple workload from AdventureWorks ScriptReplay it with sync – watch results on both clientsTurn on SSMS – ensure it is running with 128 of RAM (reboot)Turn on perfmon – ensure PLE + CPU time are addedReplay the complex one in stress + connection – watch the metrics and pause the traceAdd 2500 GB of memory to SQL server - rebootReplay the complex trace in sync and watch the countersReplay the trace with the other parameters and watch the time execution
- #24: Relax a new one is coming!
- #26: Not that many people and documentation about the featurePlay with it, test it, blog about it, talk about it. I think it matters!
- #29: Have ever considered capturing and replaying their workload?How many of you have done that? Why, how is this helpful?