SQL Server Agent Proxies
Written By: Jeremy Kadlec -- 3/14/2007
-- read/post comments
-- print --
Rating:
(not rated yet)
Rate
Problem With so many security changes in SQL Server 2005, how did the security changes affect SQL Server Agent? I have heard about SQL Server Agent Proxies, but I am not too familiar with them. How do I set them up? What dependencies do they have? What is the security benefit?
Solution In SQL Server 2000, a single configuration was available for the SQL Server Agent Proxy account. With SQL Server 2005, now 11 different proxies are available (see #1 below) for each of the SQL Server Agent subsystems. This offers a great deal of flexibility and greater security for each of these subsystems for logins and roles that do not have administrative rights to SQL Server, but need to manage SQL Server Jobs.
In order to setup the SQL Server Agent Proxy, it depends on an existing credential at the SQL Server level that maps to a Windows domain login in SQL Server. By default SQL Server does not ship with any predefined credentials, so to set one up in Management Studio for the purposes of SQL Server Agent Proxies, navigate to the root folder| Security folder | Credentials folder | right click on the Credentials folder | select the New Credential option and then enter the name, identity (Windows domain login in SQL Server) and password.
Once the credential is setup, then the SQL Server Agent Proxy must be setup. This can be achieved by the following steps:
Next Steps
- As you begin to work with SQL Server 2005, do not overlook this native functionality to improve the overall security of your SQL Server.
- Depending on your application or overall production environment, the proxies may enable you to significantly change how SQL Server jobs are managed from your SQL Server 2000 world.
- Check out these additional MSSQLTips on SQL Server Agent:
Readers Who Read This Tip Also Read
Free Live Webcast
Comment or Ask Questions About This Tip
|