by Aamod Thakur
Feedback
|
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days):
21200/
23
|
|
|
|
| Conclusion |
For more details you can refer to the MSDN Article: http://msdn.microsoft.com/en-us/library/ms178127(SQL.90).aspx
Hope This Helps. Please do reply if this post works for you
so that others can make use of the same.
|
|
|
|
User Comments
Title:
Mr.
Name:
Aamod
Date:
2010-04-27 1:58:49 PM
Comment:
Thanks Schmid, Good to know that it helped someone. N thanks for sharing the other way of solving this issue in SQL Server 2008.
Aamod Thakur
MCITP-DBA
|
Title:
Mr.
Name:
Schmid
Date:
2010-04-27 11:57:58 AM
Comment:
Hi Aamod.
This solution worked without any problems or errors. This morning I was checking the SQL Server 2008 instances on our server in preparation for migrating some Access database to SQL 2008, when I noticed the 'Agent XP's disabled' message next to SQL Server Agent for one of those instances. That's odd, I thought. The other instance showed an icon with a red circle with an x, and I could expand the node. I checked SQL Server Configuration Manager, and the settings were the same. I then found your article, ran the script, and I solved my problem.
After doing some more research, I learned that the former SQL Server surface configuration options in SQL 2005 got moved to a new View Facets window in SQL 2008. If one right-clicks on a server in Object Explorer, and then click on Facets, you are able to access all the surface configuration options, and then some! Under the Facet drop down list in the View Facets window, select Server Configuration. Under Facet Properties you will see the option 'AgentXPsEnabled'. If it is set to False, then the SQL Server Agent node is not available. Change it to True, and the node becomes available.
Of course, the code you gave makes the job quick and simple without having to go through Facets.
Cheers, Dirk
|
|
|
|
|
|
