﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Administering / SQL Server 2005  / SQL Server 2005 Resources Management / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Fri, 24 May 2013 21:41:24 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: SQL Server 2005 Resources Management</title><link>http://www.sqlservercentral.com/Forums/Topic956213-146-1.aspx</link><description>Your absolutely right Steve!:-D</description><pubDate>Fri, 23 Jul 2010 12:07:09 GMT</pubDate><dc:creator>Rick.Cornell.SME</dc:creator></item><item><title>RE: SQL Server 2005 Resources Management</title><link>http://www.sqlservercentral.com/Forums/Topic956213-146-1.aspx</link><description>Keep in mind this is for the whole server instance, not by user or job. So if you limit memory, you are limiting it for the entire instance and a job can still use most of it. Same for CPU, if you limit this to one CPU, one user/job can use all the CPU resources for that one CPU in SQL Server.</description><pubDate>Wed, 21 Jul 2010 21:26:42 GMT</pubDate><dc:creator>Steve Jones - SSC Editor</dc:creator></item><item><title>RE: SQL Server 2005 Resources Management</title><link>http://www.sqlservercentral.com/Forums/Topic956213-146-1.aspx</link><description>Thanks for ur help!</description><pubDate>Wed, 21 Jul 2010 21:07:47 GMT</pubDate><dc:creator>johnny_hsiao</dc:creator></item><item><title>RE: SQL Server 2005 Resources Management</title><link>http://www.sqlservercentral.com/Forums/Topic956213-146-1.aspx</link><description>SQL 2005 doesn't have resource Pool management like SQL 2008, so no for doing anything per user.as far as limiting to a processor you can use sp_configure and affinity mask to limit to a particular processor.  I would read up on this topic and practice it as this is not something to do on a production system [u]without a lot of testing[/u].[url]http://msdn.microsoft.com/en-us/library/ms187104.aspx[/url]As far as memory consumption you can limit the memory under the SQL instanced Server Properties | Memory | and configure the maximum amount of memory you would like to allow SQL to use.Once again this should be tested in a dev environment as limiting the amount of SQL memory will impact SQL in almost every way, more is normally better not less.   that being said I understand everyone has thier limitations they must opperate under, but be very careful adjusting any of these things as you could critically limit your server.</description><pubDate>Wed, 21 Jul 2010 07:11:35 GMT</pubDate><dc:creator>SQLBalls</dc:creator></item><item><title>SQL Server 2005 Resources Management</title><link>http://www.sqlservercentral.com/Forums/Topic956213-146-1.aspx</link><description>Can I limit some jobs or users in SQL Server 2005 using resources (CPU or Memory)?If SQL Server running on 2 CPUs host, Can I limit SQL Using CPU#1 or CPU#2 or using max 50%?</description><pubDate>Wed, 21 Jul 2010 04:15:12 GMT</pubDate><dc:creator>johnny_hsiao</dc:creator></item></channel></rss>