Introduction
Hello this is Kimberly Tripp from SQLskills. com and I'm recording this course for Pluralsight. My course is focused on SQL Server and it's titled, Optimizing Stored Procedure Performance Part 1. You're watching module 1; The Introduction. To give you a little bit of background I've written a couple of courses for Pluralsight around physical database design and optimizing Ad Hoc statement performance. And one of the things that I tend to focus on is what it takes for a database to be well tuned and well designed. And one concept that I think a lot of people, you know, think is important is, what's the code, what did I put into the code or what does my data look like or what do my table structures look like? What are my workloads and my priorities. Is it OLTP or decision support. And don't get me wrong, all of these things are important, you want to have effective code, you want to have well designed databases, you need to understand your workload, but when it really comes down to performance tuning, I think of three things. I think of course knowing your data's important, knowing your data how it's going to be used, knowing the criteria, knowing what kind of domain of values you're going to store. All of these things are incredibly important. You need to know your workload, that's important too. If I'm prioritizing for OLTP, that's probably going to have a totally different spin on performance tuning than if I am tuning for decision support. So these things are incredibly important, don't get me wrong, but the piece that I think a lot of people are missing and the thing that I try to strive to do in my classes, is showing you some of the oddities and interesting things, I think, in how SQL Server works. Because that is really the key to getting great performance.