SQL Server performs fast enough most of the time. Only the most successful companies require SQL Server Performance Tuning. Why? Because SQL response becomes too slow.
SQL Tuning is when slow performing T-SQL is messed with and all of a sudden it returns really fast. Very simple.
Most often, what we hear is “this was fast (or OK) before, and now it’s crazy slow”
There can be many reasons. Here are a few we see most often in the field:
Happens in two ways:
Don’t restart the server, or start pulling cords. You want to collect some data first. Or you won’t know why it happened. Which will pretty much guarantee the issue is going to come back.
You want to narrow down why SQL is running slow. Couple questions you want to answer:
Then depending on what the answers are, you want to narrow down to an exact T-SQL call, ideally with actual parameters that were used.
Sometimes changes can make TSQL run 20,000% faster, sometimes 50%, other times slicing 20% off the cost is great help. Bottom line – tuning results vary. They vary based on the complexity of the query, how much tuning has gone into it already, etc. But we rarely can’t make TSQL perform faster.
Make SQL Performance Tuning someone else’s problem. Hire someone. We’d love if you chose us, and we would love to help! We do tuning every day, and have done it for over a decade now!
The breadth and depth of knowledge of the Microsoft SQL Database platform and ancillary technology stack that Mark brought, has already yielded some very impressive results from both a physical and logical architecture perspective.
Mark was able to quickly identify and fix several SQL performance issues we had been struggling to trace for several weeks. Additionally, he made several other recommendations and configuration changes that had a significant positive impact on database performance.
After a weekend of work, the customer realized a 60% decrease in CPU utilization as a direct result of Mark's work.
He has mastered the understanding of complex, heavy load TSQL transactions. When tuning, database structure, indexes, stored procedure, best practices, up-time, and smooth performance are all important, Mark is the type of DBA who truly knows how to keep these high standards.