Featured Article(s)
SQL Statement Runtime in MS
The following stored procedure usp_CalcMsExecTime gets a string varchar(4000) of a SQL statement and calculates the time (in Miliseconds)it took to execute.
Additional Thoughts on Tuning
I can’t tell how many times I’ve had this conversation:
Me: "When do you want to capture the load on SQL Server so we can see what’s happening, tune the system, etc.?"
Customer: "Well, our maintenance window is 2:00a, so let’s do it then."
Me: "Um. . . well, you really need to do this during a load time that is representative of what we’re trying to troubleshoot. You know, get a look at things as the issues are happening."
Customer: "But that will slow the system down! We really have to do it off-hours."
Me: "@#^%#^@^@"
So, here’s the bit of advice for Friday. When you’re looking to troubleshoot, tune or just do reasonable due diligence on your systems, make absolutely certain that you know usage patterns. You should capture performance data and transaction information during the times where you see the issues you’re trying to solve.
My favorite example is when we were working with an insurance company – they had significant spikes between 8:00a and 9:30a, and 12:00p to 1:00p. Why? These were the time periods where people would return to their desks (either at the start of the day or after lunch) to stacks of paperwork that had to be entered and processed. It was very important, then, that we capture information about what’s going on in those periods of time so we could accurately see what was happening.
Just a bit of food for thought. It goes back to reproducing the problem – you have to be able to reproduce it so you can fix it.
Featured White Paper(s)
Managing PCI Compliance from the Database
The PCI Standard represents a far-reaching approach to data security and the protection of cardholder data. For companies see… (read more)