Diagnosing instance performance through waits, resources, monitoring, and baselines.
405 associated posts180 primary posts
Here's my favorite SQL Server books for 2016-2014:
T-SQL Fundamentals - (updated for SQL 2016) - don't be fooled by this "fundamentals" title, because everybody who writes T-SQL queries needs this book. It's the manual we should have been given when we started, and everyone's going to learn something about concurrency, performance, and updates here.
I've covered what needs to happen before you install SQL Server - now, let's talk about what to do immediately after the setup finishes.
Install not just the service packs, but also the cumulative updates.
Starting with SQL Server 2005's Service Pack 2, Microsoft releases hotfixes in cumulative packs. These updates do more than just fix bugs: they improve how SQL Server performs. These updates are free performance benefits - and who doesn't like that?
Ever wonder if you’re missing a step when you set up your SQL Server? Get a checklist to install and configure your SQL Server the right way! We've built an easy-to-follow SQL Server Setup Guide for systems administrators, DBAs, and developers that helps you prevent the most common issues we see out in the field. The guide…
Database administrators need to know each SQL Server's weakest link so we know where to focus their hardware budgets and time. On any given server, we need to know what the slowest component is, and where it'll pay off to invest hours and dollars. This is performance tuning, and the first place to start is by using Performance Monitor.
The first thing administrators want to monitor is their resources: file servers, database servers, app servers, etc. That's understandable, since they're system administrators. In order to be really successful with monitoring, though, we need to think like customer administrators - for both our internal and external customers. Forget the hardware, and think about the people. How do our customers interact with our systems?
