1. Testing With Your Data, Your Way! Distributed Replay 1 SQLSat 470 Washington DC December 5, 2015

2. Melody Zacharias Consultant Chapter Leader / Regional Mentor for Canada http://sqlmelody.blogspot.ca/ SQLMelody@gmail.com @SQLMelody ca.linkedin.com/in/melodyzacharias

3. Agenda distributed replay? is it used for? do we set it up? 3 What Why How

4. 4

5. Why Bottle Neck 5

6. Why 6

7. Why - Limitations Step Run to Cursor Toggle Breakpoint 7

8. 8

9. What Administration ToolReplay ControllerReplay Client(s)Target Server 9

10. What 10

11. What – Administration Tool 11

12. What - Controller 12

13. What - Clients 13

14. What – Target 14

15. 15

16. How Configuration Collection Replay Results 16

17. Configuration 17

18. Configuration C:\Program Files (x86)\Microsoft SQL Server\110\Tools Controller configuration file DReplayController.config Client configuration file DReplayClient.config Preprocess configuration file Dreplay.exe.preprocess.config Replay configuration file Dreplay.exe.replay.config

19. Configuration - Preprocess 19

20. Configuration - Controller 20

21. Configuration - Controller 21

22. Configuration - Client 22

23. Configuration - Replay 23

24. Target instance Sequencing Stress scale granularity Connect timescale Think time scale Use connection pooling Health monitor interval Query time out Threads per client Configuration 24 Replay Configuration

25. Configuration 25

26. Configuration Restart the services on all the servers NET STOP “SQL Server Distribute Replay Controller” NET START “SQL Server Distribute Replay Controller” NET STOP “SQL Server Distributed Replay Client” NET START “SQL Server Distributed Replay Client” On each server that has the services installed 26

27. Configuration The Rest of the Story....... 27

28. Configuration Check for errors C:\Program Files (x86)\Microsoft SQL Server\110\Tools\DReplayClient\Log Failed to connect controller with error code 0x80070005 Error code 0x80070005 means “Access is denied” 28

29. Component Services

30. Configuration 30 Start -> Run and type dcomcnfg

31. Configuration 31

32. Configuration 32

33. Configuration 33

34. Configuration Restart the services on all the servers NET STOP “SQL Server Distribute Replay Controller” NET START “SQL Server Distribute Replay Controller” NET STOP “SQL Server Distributed Replay Client” NET START “SQL Server Distributed Replay Client” On each server that has the services installed 34

35. Configuration Check the Distributed Replay Client log file C:\Program Files (x86)\Microsoft SQL Server\110\Tools\DReplayClient\Log “Registered with controller ” “Failed to connect controller with error code 0x800706BA client may not connect to controller “ 35

36. Fire Wall

37. Configuration 37

38. Configuration 38

39. Configuration 39

40. Configuration 40

41. Configuration 41

42. Configuration 42

43. Configuration 43

44. Configuration Restart the services on the server NET STOP “SQL Server Distributed Replay Client” NET START “SQL Server Distributed Replay Client” 44

45. Configuration - Verify Log files 45

46. Let the games begin

47. 47 Collection

48. Demo

49. Collection 49

50. Trace Events 50

51. 51 Trace File

52. Collection 52

53. Collection 53

54. 54 DReplay preprocess -i input_trace_file -d controller_working_dir [-m controller] [-c config_file] [-f status_interval] Collection

55. Replay 55

56. Replay DReplay replay -d controller_working_dir -w clients [-o] [-m controller] [-s target_server] [-c config_file] [-f status_interval] 56 c:\>DReplay replay –d c:\DistRePlay –w client1, client2

57. Results 57

58. 58

59. Application load testing Physical vs Virtual computing Metrics for distributed computing TDE load System upgrades Hardware upgrades Index tuning UsesResults Tables Graphs Analytics Metrics Usage and Presentation 59

60. Results – Read Latency

61. 61

62. 62 PowerShell

63. 63 Change in Domain

64. Controller configuration file DReplayController.config Changes location when you change domains Client configuration file DReplayClient.config Modify location in the configuration 64

65. Common issues Error DReplay The client ‘ClientServerName’ is not a registered distributed replay client. Make sure that the SQL Server Distributed Replay Client services is running on ‘ClientServerName’, and that the client is registered with the controller ‘localhost’. 65

66. Common issues 66 Empty Result set

67. QUESTIONS

68. Resources Distributed Replay: http://bit.ly/1OQUhGA Requirements including events: http://bit.ly/1GRIiC6 Parameters for Replay: http://bit.ly/1Gh8Gum My Blog: SQLMelody.blogspot.ca My Email: SQLMelody@gmail.com 68

69. Thank You