What do all three of those things have in common? Here’s a hint: it’s me!
That’s right, this weekend I will be at SQL Saturday #53 in Kansas City. I am especially looking forward to the BBQ crawl on Friday afternoon followed by the Royals game that night. I’ll pick up a KC cap while at the park and add to my collection of baseball hats bought at major league parks (I have five (ANA, ATL, COL, NYY, TEX) and it would be six but I don’t see the need to buy a Red Sox hat at Fenway anytime soon). One aspect of SQL Saturdays that I enjoy is being able to soak up some local flavors while there (hint for future organizers of SQL Saturdays everywhere…do something that showcases your city to others when possible).
Here is a quick summary of my upcoming talk this Saturday:
What Are You Waiting For?
It’s a simple question, right? But how often do you have the answer, especially for your SQL statements? Thomas LaRock from Confio Software will teach you how proper response time analysis plays a key part in the overall performance tuning process. You will learn how to define, measure, and analyze performance issues as well as implementing changes and how to make sure those changes continue to have the desired effects.
This talk is also known as “Performance Tuning Made Easy”, and it is related to another upcoming talk of mine, a webinar next Thursday (you can register here):
SQL Server Performance Tuning Made Easy
Traditional performance tuning tools and methodology are largely inefficient for solving problems quickly. Learn how to put a performance tuning process – based on the concept of Performance Intelligence – into your work routine that will save you time, your company money, and allow you to be more proactive.
The talks I have been giving this fall have been focusing on one thing: make performance tuning easier. Too many people are overwhelmed when it comes to performance tuning. When I ask people to describe their performance tuning process it usually goes like this:
Step 1. Wait for the phone to ring.
Step 2. Answer it.
Step 3. Listen to someone complain.
Step 4. Try to get them to stop complaining by fixing whatever it is that is causing them pain.
And that sums up roughly 90% of everyone I ask. Back in July I started to outline a process that would give people some structure in order to help them tackle performance issues, help them focus their efforts on the exact spot they need to be looking at, to help them be more efficient. I see a lot of great information available (books, blogs, classes, cruises, etc.) that helps to teach people about how SQL Server works, but few if any of these lessons ever give people the structure they need to take with them back to the office on Monday and be more productive.
That’s my goal. Come listen to me this Saturday and tell me how close I get.
