SQL Server CMS – where are locally registered servers stored

In one of my previous posts I showed you how to register multiple instances in SQL Server Management Studio Registered Servers explorer. However registering them locally has its pitfalls such as not being accessible for other DBAs without being imported/exported from the GUI. This operation is not that complicated itself, but it got me curious where are those registered instances stored after all so I do not have to export and import anything. It took me a bit longer to find it, but I did it. So, if you are curious too, those instances are stored in an XML file stored on the following paths:

Windows Server 2003 based systems: C:\Documents and Settings\<user>\Application Data\Microsoft\Microsoft SQL Server\100\Tools\Shell\RegSvr.xml

Windows Server 2008 based systems: C:\Users\<user>\AppData\Roaming\Microsoft\Microsoft SQL Server\100\Tools\Shell\RegSvr.xml

The XML file is structured just as the one, created after exporting registered servers from the GUI. So you can just copy it and restore it wherever you desire.


Automating Administration Across an Enterprise

The goal of automating administration across a large organization is aiming at simplifying the day-to-day job  of the DBA and also ease some dataflow tasks between two or more servers.

By definition multiserver administration is administering two or more instances and with it you can do:

  • Manage two or more servers
  • Schedule information flows between enterprise servers for data warehousing.

Implementing multiserver administration with SQL Server is part of the SQL Centralized Management Solution provided in Codeplex here. Multiserver administration covers the part with Master-Target server of SQL Server Agent Jobs.

Link to the MSDN article on the subject you can find here.