SP Config DB still pointing to old DB server

We changed the SharePoint 2016 SQL server recently. Once alias is set to new SQL server, sites were working fine. But when I checked in CA, Configuration Database still points to old DB server (under manage servers in the farm).

The content databases pointed to new sql server. Only the config database still points to old server.

I tried to run config wizard, it is pointing to the new sql alias in the initial screen, but execution failed with error saying "An update conflict has occurred, and you must re-try this action."

I stopped the SQL services in the old server to check if the connections now point to new server. But then the sites and CA did not open and showed run time error.

So I restarted the SQL server and tried to run the config wizard, same error.

I tried to detach the config db from old SQL server but then CA did not load.

How do I change the sql server pointed by co

nfig db?

Hi Ranjani Raja, you can try the following:

Backup Your Farm and Databases:
- Before proceeding, make sure to take a full backup of your SharePoint farm and all associated databases.
Set Up a SQL Alias:
- Launch SQL Server Configuration Manager on each SharePoint server.
- Navigate to "SQL Native Client Configuration" > "Aliases".
- Create a new alias that points to your new SQL server. The alias name should match the old SQL server's name.
Update the Configuration Database Connection String:
- Open PowerShell with administrative privileges on the SharePoint server.
- Execute the following commands to change the configuration database instance:
```
$configDB = Get-SPDatabase | Where-Object { $_.Type -eq "Configuration Database" } $configDB.ChangeDatabaseInstance("")
```
Verify the Alias Configuration:
- Ensure that the alias is correctly configured to point to the new SQL server on all SharePoint servers.
- Restart the SharePoint Timer Service on all servers by running:
```
net stop SPTimerV4 && net start SPTimerV4
```
Run the SharePoint Configuration Wizard:
- Open the SharePoint Products Configuration Wizard.
- Proceed through the prompts to confirm that the configuration database is pointing to the new SQL server.
- If the wizard fails, check the ULS logs for detailed error messages.
Test Database Connectivity:
- Stop the SQL services on the old server once more and verify that SharePoint sites and Central Administration are operational.
- If everything is working correctly, you can decommission the old SQL server.
Update Alternate Access Mappings (AAM):
- If applicable, update any references to the old SQL server in the Alternate Access Mappings.

Following these steps will help you successfully redirect the SharePoint configuration database to a new SQL server. Should any issues arise, consult the ULS logs and the event viewer for more specific error details.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Sigar Dave2y ago
Hi Ranjani Raja, you can try the following:
1. Backup Your Farm and Databases:
  
  Before proceeding, make sure to take a full backup of your SharePoint farm and all associated databases.
2. Set Up a SQL Alias:
  
  Launch SQL Server Configuration Manager on each SharePoint server.
  
  Navigate to "SQL Native Client Configuration" > "Aliases".
  
  Create a new alias that points to your new SQL server. The alias name should match the old SQL server's name.
3. Update the Configuration Database Connection String:
  
  Open PowerShell with administrative privileges on the SharePoint server.
  
  Execute the following commands to change the configuration database instance:
  
  $configDB = Get-SPDatabase | Where-Object { $_.Type -eq "Configuration Database" } $configDB.ChangeDatabaseInstance("")
4. Verify the Alias Configuration:
  
  Ensure that the alias is correctly configured to point to the new SQL server on all SharePoint servers.
  
  Restart the SharePoint Timer Service on all servers by running:
  net stop SPTimerV4 && net start SPTimerV4
5. Run the SharePoint Configuration Wizard:
  
  Open the SharePoint Products Configuration Wizard.
  
  Proceed through the prompts to confirm that the configuration database is pointing to the new SQL server.
  
  If the wizard fails, check the ULS logs for detailed error messages.
6. Test Database Connectivity:
  
  Stop the SQL services on the old server once more and verify that SharePoint sites and Central Administration are operational.
  
  If everything is working correctly, you can decommission the old SQL server.
7. Update Alternate Access Mappings (AAM):
  
  If applicable, update any references to the old SQL server in the Alternate Access Mappings.
Following these steps will help you successfully redirect the SharePoint configuration database to a new SQL server. Should any issues arise, consult the ULS logs and the event viewer for more specific error details.
0