Contents
Normally, all that is required to add a database server to an existing SharePoint farm is to set up and configure a new database server and join it to the farm by referencing the new server when you add a feature or move database content to the new server.
APPLIES TO: 2013 2016 2019 SharePoint in Microsoft 365 You can add more database servers at any time to respond to business or operations requirements. Because a database server contains the farm content, which can consist of diverse types of data and can have a fast growing document collection, the size of the farm databases can grow quickly.
How to copy configuration settings from one farm to another?
There are many ways in which you can copy configurations from one farm to another. Determine which method to use based on the configuration settings that you want to copy and how often you have to copy them. Back up and restore a farm without the content databases attached.
What to do if SharePoint farm is unsupported?
If the wrong content database is being referenced, detach it and attach the content database residing on the new SQL server. Here’s the steps you need to do each. Cloning a SharePoint farm is hard. It might even be unsupported through Microsoft. And as a bonus: It’s especially useful to make an automated installation in desaster recovery scenarios.
1) Run SQL Server installation. 2) On the Setup Role page, select SQL Server Feature Installation. 3) On the Feature Selection page, select Reporting Services add-in for SharePoint products. 4) Click Next on the next several pages to complete the setup options.
1) In SharePoint Central Administration, click Manage servers in this farm in the System Settings group. 2) Verify the new server is in the list. Update your NLB solution. If appropriate, update your hardware or software NLB environment to include the new server.