Replay your workload as it is your actual one!
•Transferir como PPTX, PDF•
0 gostou•1,049 visualizações
Have you ever wanted to replay your application workload be that because you upgraded to a new hardware, added new indexes or something else? Now there's a feature for that! It's called Distributed Replay and in this session you will learn how this new feature in SQL Server 2012 can help you resolve that problem!
Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Replay your workload as it is your actual one!
Semelhante a Replay your workload as it is your actual one! (20)
Mais de Boris Hristov
Mais de Boris Hristov (20)
Último
Último (20)
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
- 2. Sponsors
- 3. So who am I? @BorisHristov
- 4. How many of you…
- 5. Possible scenarios: 1. Application compatibility 2. Performance / Load testing 3. Forecasting
- 6. What tools did we have till now?
- 9. These are cool… … but are just 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 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 inbound 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 2. Distributed Replay is quite a powerful tool! 3. Don’t be afraid of not having a GUI 4. Capture -> Preprocess -> Replay 5. Document, blog, share it with the community!
- 25. Resources Channel 9 - Joe Sack(SQLSkills) Intro and Demo blog posts Jonathan Kehayias(SQLSkills) Intro and Demo blog posts Microsoft Peace of Mind Video MSDN Documentation Distributed Replay GUI (in beta) … you and me now
- 26. Thank you!
Notas do Editor
- Радвам се да ви видя! Ще си поговорим за функционалност, която ако познавате добре ще успеете да блеснете в критичен момент за вашия бизнесъпгрейд към нова версияъпгрейд на хардуера / към нов хардуерпланиране и прогнозиране на натоварванетоDistributed Replay
- Дано в другите зали да не се очудят ако ни чуят, но нека вдигнем настроението!
- Have ever considered capturing and replaying their workload?How many of you have done that? Why, how is this helpful?
- Application compatibility meaning both upgrade or migration of the app
- The maestro!
- The maestro!
- http://support.microsoft.com/kb/944837Problems with SQL Server 2012 …
- but you know the words – it’s not cool enoughSCALE is your word!
- What is this doing actually? Few words about the functionality.
- Thank god there is no support for SQL Server 2000 anymore…Developer – DR Controller allows just 1 clientDR Controller feauture - 160 MB DR Client - 1.9GBCan be installed via Parameters – DREPLAY_CTLR , DREPLAY_CLT, TOOLS
- Administration tool – you have to install the Management Tools
- 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 networkAD -> Firewall: doneClient: doneDC -> Firewall -> doneClient -> Not doneManagement tools -> DoneDRController – not use FQDN – show it but not installbbbController: DoneAccess – not set for all accounts
- Have ever considered capturing and replaying their workload?How many of you have done that? Why, how is this helpful?
- TO CHECK – CAN I ADD MORE COLUMNS to the events
- Sorts the events in ascending order based on EventSequenceTrims away all events and columns that are not replayable
- Per connection and limit the connection time scale + thinktime scale -> users are logging almost together
- PHOTO ! (green text)
- 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 – 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
- Not that many people and documentation about the featurePlay with it, test it, blog about it, talk about it. I think it matters!
- If less events are selected – Input trace is not valid.