First published on TECHNET on Apr 29, 2015
The Service Manager setup allows the admin to install SQL Always on with default or with single instance name only and doesn’t provide flexibility to have multiple instance names. This limitation is with the fresh installation of Service Manager, but all SQL Always on scenarios work without any issue with migration of Database (including SQL Always On + FCI).
Please follow these steps to migrate SMDB to SQL Always On
Prepare the SQL Always on setup separately, you can also consider SQL Always On + FCI
Create an AGL (Availability Group Listener), provide the appropriate port number and avoid the default port 1433. For example AGL name =
and AGL Port =
Open the inbound port for SQL Server Instance and AGL on each SQL Server machine
You can refer this article with following exceptions:
In Step 5#
Configure the Service Manager database
“To Configure Service Manager tables”
Use the <AGL Name,AGL Port number> instead of the computer name hosting the Service Manager database, for example SMListener,5122
In Step 6# Use the <AGL Name,AGL Port number> to update the both DWStagingAndConfig database tables.
In Step 7#
“Configure the registry on all the management servers”
Change the registry key HKEY_LOCAL_MACHINESoftwareMicrosoftSystem Center2010CommonDatabase give DatabaseServerName as <AGL Name,AGL Port number>
The net result here is that, we are changing the computer name hosting the Service Manager database to
<AGL Name,AGL Port number>
for SQL Always on support.