Export (0) Print
Expand All

Importing Data (Master Data Services)


Applies To: SQL Server 2016 Preview

You can populate the Master Data Services database with data from your organization's disparate data sources. For data to be in the appropriate Master Data Services database tables, you must import data into staging tables and then process the staged data as a batch.

You can use the staging process to:

  • Create, update, deactivate, and delete leaf and consolidated members.

  • Update attribute values.

  • Designate relationships in explicit hierarchies.


In SQL Server 2016 Community Technology Preview 2 (CTP2), support for the SQL Server 2008 R2 staging processes is deprecated.

The Master Data Services database includes three staging tables that you can populate with your organization’s data. After you populate these tables, initiate the staging process to load the data from the staging tables into the appropriate MDS tables.

The name of each table is specified when an entity is created and cannot be changed. If the staging table name contains a _1 or other number, another table of that name already existed when the entity was created.

Table Name



Create, update, and delete leaf members and their attributes.


Create, update, and delete consolidated members and their attributes.


Move members in an explicit hierarchy.

You can initiate the staging process by using stored procedures or by using the Master Data Services web application.

The Master Data Services database includes stored procedures associated with the staging tables. Use these stored procedures to load data from the staging tables into the appropriate MDS tables. The stored procedures are named similarly to the associated tables:

  • stg.udp_name_Leaf

  • stg.udp_name_Consolidated

  • stg.udp_name_Relationship

For more information on these stored procedures, see Staging Stored Procedure (Master Data Services).

You can use the web application’s Integration Management functional area to start the staging process. The staging process in the UI is started at intervals determined by the Staging batch interval setting in Master Data Services Configuration Manager.

All transactions that occur when data or relationships are imported or updated can be logged. An option in the stored procedure allows this logging. If you initiate the staging process from the Master Data Services web application, no logging occurs.

In Master Data Services Configuration Manager, the Log staging transactions setting does not apply to this method of staging data.

When you load data by using the staging process, the data is not automatically validated against business rules. You must validate the data manually or by using a stored procedure.

For more information on what validation is and when it occurs, see Validation (Master Data Services).

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2015 Microsoft