Microsoft SQL Server 2012 Bible
by Adam Jorgensen, Jorge Segarra, Patrick LeBlanc, Jose Chinchilla, Aaron Nelson
Chapter 50
Resource Governor
In This Chapter
Understanding Fundamentals
Using Performance Monitoring of the Resource Governor
Exploring Views and Limitations
It's a DBA's nightmare. A query runs and eats up resources to the point that everything else slows to a crawl. The fault might belong to a software developer who didn't consider the resources that his queries chew up, but you get the call. And saying that you don't know what the problem is won't satisfy anyone.
You might get to the bottom of the problem, but what then? Do you sever the connection that the errant application comes in on? That could be a disaster for a mission-critical process. These issues challenged SQL Server DBAs in the past.
The 2008 release of SQL Server introduced the Resource Governor feature, which enables you to limit the CPU and memory usage by a specific application, hostname, user, or any other attribute of the connection session. Now you can stop having those nightmares because you can limit the resources for a query that might typically bring the server to a crawl.
Resource Governor is also an Enterprise Edition-only feature.
You can configure the Resource Governor in two ways. The first is through T-SQL commands. The second is via the Object Explorer from within SQL Server Management Studio.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access