thomashohner (10/23/2016)
Thanks Jeff,After I posted I thought about it more and I guess the SAN made it kind of a moot point. Grant basically states at the beginning of the book that most performance issues are related to the query. I guess i was trying to score a easy configuration win. So far query tuning feels more like a art than a science. Going to keep studying and practicing. It feels frustrating sometimes you feel like wow I just solved a major performance problem and then like 2 weeks later its back with a vengeance. You then realize I solved nothing just band aided it. Got my highlighter going to see if I can do another chapter.
Thanks again !:-)
You're definitely reading the best book on the subject. Grant did a marvelous job on the original and the update.
Shifting gears... as you read the book, keep in mind the one thing that people forget. Grant didn't explicitly state it but the whole goal of "performance tuning" isn't necessarily to tune for performance. It's much simpler than that. A whole lot of very smart people wrote SQL Server and it works great. The problem is when people write things where SQL Server isn't so great but it will still do it's damnedest to provide what it's being asked for.
To state it more simply, performance tuning isn't about forcing SQL Server to do great things. It already does that. Performance tuning is all about [font="Arial Black"]letting [/font]SQL Server do what it does best.
The first step to performance tuning can be found in the paradigm shift that can be found in my signature line below. Then, remember that an index is nothing more than a subset duplication of data with it's own "sort order" that lives in a table with columns (and rows) and Grant's book will get a whole lot easier to understand. At least that's what worked for me.
--Jeff Moden
Change is inevitable... Change for the better is not.