Contents
A: Yes it is possible, we can have more than one SQL instance where we can store the content databases. If you want to transfer a SharePoint content database from one instance to another you can use the following procedure:
In Central Administration, in the Application Management section, click Manage Content databases. On the Manage Content Databases page, click Add a content database. On the Add Content Database page, verify that the Web Application menu displays the correct web application. In the Server box, specify the database server that hosts the database.
How to move databases from one SharePoint Server to another?
To move all databases from one database server to another database server, you have to work in both SharePoint Server and SQL Server. Before you begin this operation, review the steps in this process: Prepare the new database server. Close all open SharePoint Management Shell windows.
How to move content databases in SQL Server?
In SQL Server Management Studio, open the source SQL Server instance, and then expand the Databases node. Right-click the content database, point to Tasks, and then click Detach. Repeat this step for each content database that you want to move. Use this procedure to move only content databases. Do not detach any other kinds of databases.
The SharePoint Server 2016 application is built on the SQL Server database engine. Most content and settings in SQL Server 2014 (SP1), SQL Server 2016, and SQL Server 2017 RTM are stored in relational databases.
The minimum requirements for a database server in SharePoint Servers 2016 and 2019 are as follows: 64-bit edition of Microsoft SQL Server 2014 with Service Pack 1 (SP1) SQL Server Express is not supported with SharePoint Servers 2016 and 2019. SQL Server 2017 on Linux is not supported with SharePoint Servers 2016 and 2019.
How to transfer a database from one SharePoint to another?
If you want to transfer a SharePoint content database from one instance to another you can use the following procedure: On the SQL server1. Backup the content database. 2. Restore the database on the second instance 3. Add the same permissions for the content database that you had on the source instance. 4.