Maria's journey in the data fields

There is an easy way to open several connections to your SQL Server in order to perform load testing. You can use Management studio "Multiple Server Query Execution" feature. This feature is usually used to run the same query against multiple servers but we also can use it for a load or stress testing. In the registered servers tab create a group with the same name as your server that you are planning to use for the load testing. Inside the group create 10 or more connections to the same server, just making sure that in the server alias field you add number to your server name otherwise Management Studio will not allow to create two server connections with the same alias. Easy way to add multiple connections is by editing Management Studio connections xml file that you can find in "C:\Users\<> \AppData\Roaming\Microsoft\Microsoft SQL Server\110\Tools\Shell\RegSrvr.xml", you can simply copy the connection multiple times, still changing alias name for each ne...

Are you familiar with Trace Replay feature SQL Profiler? It's not really popular but actually can do a lot for you. Replay is the ability to save a trace and replay it later. This functionality lets you reproduce activity captured in a trace. When you create or edit a trace, you can save the trace to replay it later. Replaying trace is useful when - you need to troubleshoot production issues then you can run recorded trace against fixed application to make sure all bugs were fixed. - you need to simulate production load on QA/dev environment for stress testing - test new code that is written on development server by simulating real DML load. The process of recording and replaying trace is really easy. - Use preconfigured replay template (TSQL_Replay) because, if you do not capture all required data, SQL Server Profiler will not replay the trace (!) - Save the trace using any format: table or trace file. If you want to use rollover files with limited size take into consideration the...