Skip to main content

How to Move the Service Manager SharePoint Portal Database

Author by Christopher Mank

Throughout the life-cycle of your Service Manager infrastructure, there may come a time when you need to move some of the components from one server to another.  There already exists some great documentation on how to move the Service Manager and Data Warehouse databases (found here), but what about the SM SharePoint Portal database? Since the SM portal is built on SharePoint 2010, we can refer to that documentation on how to move the database.  Here are the steps: 1.  Browse out to the following TechNet article on how to move all databases related to your SharePoint 2010 environment.  Complete steps 1-7. Move all SharePoint 2010 Databases 2.  Up to this point, all we've really done is prep the new server, stop all services so nothing can write to the databases and then move the databases from the old server to the new server.  Step# 8 is where the real magic happens.  How this all works is by creating a connection alias on the SharePoint server to the new SQL server.  So even though the database still has the old server name, the connection alias tells SharePoint that when a request is initiated to the old server that it should really connect to the new server. Step# 8 indicates to complete this step by setting up an alias in SQL Server Configuration Manager.  Although you can complete this step using SQL, you most likely will not have SQL loaded on your main SharePoint server.  So instead of installing SQL to complete this step, you can use the SQL Server Client Network Utility to complete this, which comes loaded by default with Windows. To access the SQL Server Client Network Utility: A.  Click Start --> Run and enter "cliconfg" B.  Click on the Alias tab to setup the Alias SSCNU Image Here is the key point.  What this utility is actually doing is setting a reg key for this alias.  However, it is only setting the alias in the x86 directory.  So to properly complete this alias, setup the following reg key in both of these directories. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo sql alias reg key image 3.  Once you have the alias setup for both x86 and x64, the last step is to restart the services in the farm (Step# 9 from the TechNet documentation). All you need to do now is connect to the SCSM portal and it should load without issue.  And that's all there is to it.  I hope this helps those trying to move the Service Manager Portal Database. Until the Whole World Hears, Christopher

Christopher Mank

Systems Architect