Some quick steps that I take to configure a SQL alias for SharePoint when moving from one SQL server to another.
Don’t believe the SQL Admin has configured network access for the SQL Server service.
- Login to the new SQL server and verify that TCP/IP is enabled.
- Launch SQL Server Configuration Manager
- Drill into SQL Server Network Configuration
- Open the properties for TCP/IP
- On the IP Address tab and enable TCP/IP on the appropriate IP Address.
- Restart the SQL Server service for that instance
- Disable or configure the Windows Firewall on the SQL server
On the SharePoint servers, configure the SQL alias…twice
- Launch C:\windows\syswow64\cliconfg.exe.
- Select the alias tab, new, TCP/IP
- In the server alias field enter the old_SQL_server\instance
- In the Connection parameters server name enter the new_SQL_server\instance
- Repeat the process for the FQDN of both servers, e.g. server.domain.local\instance
- Launch C:\windows\system32\cliconfg.exe and repeat the process again.
- Select the alias tab, new, TCP/IP
- In the server alias field enter the old_SQL_server\instance
- In the Connection parameters server name enter the new_SQL_server\instance
- Repeat the process for the FQDN of both servers, e.g. server.domain.local\instance
Script out the SharePoint service accounts from the old SharePoint SQL Server and back in on the new one. (SQL 2012)
- Launch management studio
- Drill into Security > Logins
- For each of the SharePoint service accounts –
- Right click on each login
- Script Login as > Create to > File
- Run the scripts on the new SQL server for each account.
Restore your database from the other server
- Like the title says, restore the DB’s
SharePoint should render fine. Remember to test central admin as well as one of the other web apps.
[aboutme username=”ashley.lawrence”]