Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Copying SharePoint Objects as a Separate Action Self-Service Migration Incremental Migration Log Files Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix
Registering Metalogix Command DLL Files Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed and Self-Service Migration Frequently Asked Questions
DB_Owner Permission Migrating with the Fabulous 40 Templates Item Count Discrepancies Keyboard Shortcuts License Key Troubleshooting Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Using Proxies, Load Balancing or Alternate Access Mappings Troubleshooting the Extensions Web Service Installing the Extensions Web Service on Specific Systems Extensions Web Service Installation Files Using Older Versions of the Extensions Web Service Preserving IDs when Migrating a Custom List as a Folder Migrating JavaScript Migrating Site Variations Migrating with SharePoint 2010/2013/2016 Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations SharePoint 2013 and 2016 Site Collection Creation Issue Job List Database fails to Load After Upgrade Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs with a CSOM Connection Type Retrying Failed Document Copies to O365 CSOM Connections Migrating Content When the Source Custom List Template is Missing Are SharePoint Online Migrations Throttled? What to Expect when Migrating with StoragePoint on the Target Migration Error Message 'There was an Error Reading from the Pipe: The Pipe has been Ended (109, 0xd6)' How do I Remove Items from My Azure Blob Storage Account? Azure Batches Getting Stuck Supported Nintex Actions for SPO Migration "Insufficient Credentials" Message Connecting to Modern Team Site Using Web Browser Authentication Error Making a Browser-Based Connection with PowerShell Console Open
About Us

Connecting to a SharePoint Database

This connection type is read only, and is typically used as the primary connection type when connecting to SharePoint 2003 instances (SPS 2003 and WSS 2.0), although it can also can be used for SharePoint 2007, 2010, 2013 and 2016. .   In case of performance concerns, this connection type can also help, as the source data would be read directly from the database, and does not have to go through the source SharePoint APIs.

NOTE: Connecting to a SharePoint 2013 or 2016 database is supported:

·from a server where the corresponding version of SharePoint is installed


·from a non-SharePoint 64-bit machine that has had the compatible version of the SharePoint Database Adapter configured via the Content Matrix Console installer.  (Remember that if you need to switch from one version of the database adapter to the other, you will need to first uninstall and then re-install the SharePoint Edition in the Controller using Modify operation. If you are using Distributed and/or Self-Service Migration, you will also need to update the database adapter version on the agents/workstations.)

To connect to a SharePoint database:

1.In the ribbon menu, choose Connections > Connect to SharePoint Database to display the Connect to SharePoint SQL Server dialog.

Connect to SP Database

2.For SQL Server, either

§Manually enter the name or IP address for the SharePoint Database you want to connect to.


§Chose a previously accessed SQL server from the drop-down.


§Click [Browse] then navigate to and select either a Local or Network SQL server.

SQL Server Browser

NOTE: : Remote connections must be enabled in order for Metalogix Content Matrix to connect to any Databases on the Network tab.  

3.For Authentication User Current Windows user, either:

§ Accept the default (Use Current Windows user)


§Select Use SQL Server login and enter the credentials used to authenticate with the selected SQL Server.

4.Click [Connect].

The Connect to SharePoint SQL Server dialog displays all of the SharePoint databases within that connection.


NOTE: Any SQL or SharePoint server nodes that are unavailable will be marked with an "x" through the node. The three most common reasons are:

·the specified user doesn't have permissions to access that particular Database

·the Database is not a SharePoint schema Database

·the connection is being made from a machine that does not have SharePoint installed to a SharePoint 2013 or 2016 Database using an incompatible adapter.  (Remember that you are prompted to specify the DB adapter when installing Content Matrix Console on a non-SharePoint machine.  Since you cannot have both adapters on the same machine at the same time, you can change from one to the other by uninstalling then re-installing the SharePoint Edition using the Modify operation.)


§select a database (which will include all of the sites within that database)


§Expand the database node and select a single site collection or site within the database.

6.Select the desired node, and click [OK].

The Set Host Name dialog displays.


7.Use the information in the following table to determine the appropriate action to take.

If …

Then …

·you are planning to use Link Correction as part of the migration

Enter the Host Name in the format "http://<ServerName>:<PortNumber>"

For example, if connecting to a SharePoint DB for a system that has the web URL of http://2010foundation:1818, you would want to use that as the Host Name, even though the database name will be different.


When connecting to a Database, the URLs for links that point internally to the SharePoint server have a different format, which would prevent link correction. The host name is used to replace the different formatting from the DB connection, enabling links will be viewed in the proper format.

you are not planning to use Link Correction as part of the migration

Click [Skip].

NOTE: It is possible to go back and set the Host name after a database connection has been made. To do this, select the DB connection, right-click, and choose Properties. In the Properties dialog click the [...] button at the end of the Host column, and this will open the Set Host Name dialog, allowing this value to be edited.

The selected node will now appear in the Explorer view.

Setting the Template Path for a Database Connection (When Using Link Correction)

If you are planning on using Link Correction, your Database (DB) connection must point to a specific file location from which to fetch template data. The specified folder location must contain all of the templates that will be used.

1.In the Explorer view tab, navigate to the Database connection for which the template location should be specified.

2.Select the root node of the DB connection, right-click and choose Properties.

3.In the Node Properties dialog line, click the [...] button to the right of the Template Path field, then select the folder that contains the template data.

4.Click [OK].

The following warning message displays:

Changing this setting impacts how data is read from this connection.  If there are any actions currently running that use this connection, changing the setting may invalidate their results.  Continue?

5.To continue, click [OK].

The specified folder location is now listed next to the Template Path line, and all the template data for the DB connection will be called from this location.

Additional Requirements for O365 Tenant Connections

Metalogix Content Matrix Console can make a tenant level connection to a SharePoint O365 environment. A tenant level connection works the same as a CSOM connection to an O365 environment, with the exception that the tenant connection can also migrate Site Collections, MySites, Modern Team Sites, and Managed Metadata. While a tenant connection is similar to the CSOM connection type, the process of creating the connection is slightly different, and also involves some prerequisite steps to set up permissions.

Required Permissions for Connecting to an O365 Tenant

In order for users to make an O365 tenant-level connection, the connecting user must have the Global Administrator permissions in the O365 tenant environment, as well as Site Collection Administrator permissions for each site collection being migrated.

Refer to  the Office Support article Assigning admin roles in Office 365 for details.

If the connecting user does not have sufficient permissions, the connection will not be completed and the following connection error will display:

O365 Tenant Authentication Error

· For a  SharePoint Online connection, you must select one of the Web Browser Authentication options if the Connect As account:

§uses "modern" (not "legacy") authentication methods.  (For more information about legacy vs. modern authentication, refer to the Microsoft Support article How modern authentication works for Office 2013 and Office 2016 client apps.)


§is part of a SharePoint Online Multi-Factor Authentication Policy.

Related Documents