Skip to content

Latest commit

 

History

History
103 lines (64 loc) · 6.17 KB

File metadata and controls

103 lines (64 loc) · 6.17 KB
title Data Import (Master Data Services) | Microsoft Docs
ms.custom
ms.date 06/13/2017
ms.prod sql-server-2014
ms.reviewer
ms.technology master-data-services
ms.topic conceptual
helpviewer_keywords
staging process [Master Data Services], about staging process
importing data [Master Data Services]
staging process [Master Data Services]
ms.assetid 181d1e22-379c-45d1-b03c-e1e22ff14164
author lrtoyou1223
ms.author lle
manager craigg

Data Import (Master Data Services)

Once you've created a model for your data in [!INCLUDEssMDSshort], you can start adding data and make changes to data in the [!INCLUDEssMDSshort] database. You use [!INCLUDEssMDSshort] staging tables, stored procedures and Master Data Manager .

You can also use the [!INCLUDEssNoVersion][!INCLUDEssMDSshort][!INCLUDEssMDSXLS], to add data to the MDS repository ([!INCLUDEssMDSshort] database). For more information, see Publishing Data (MDS Add-in for Excel).

When you add and update data, you can do the following.

  • Load and update members, and update attribute values

  • Deactivate and delete members

  • Move explicit hierarchy members

Adding and updating data includes the following main tasks.

  1. Load data into the staging tables in the [!INCLUDEssMDSshort] database.

  2. Load the data from the staging tables into the appropriate [!INCLUDEssMDSshort] tables.

    You use staging stored procedures or [!INCLUDEssMDSmdm] to load the data.

Note

In [!INCLUDEssSQL14], support for the [!INCLUDEssKilimanjaro] staging processes is deprecated.

Deactivating and Deleting Members

Deactivating means the member can be reactivated. If you reactivate a member, its attributes and its membership in hierarchies and collections are restored. All previous transactions are intact. Deactivation transactions are visible to administrators in the Version Management functional area of the Master Data Manager.

Deleting means purging the member from the system permanently. All transactions for the member, all relationships, and all attributes are permanently deleted.

Note

You cannot use staging to reactivate members. You must do it manually in the Master Data Manager. For more information, see Reactivate a Member or Collection (Master Data Services).

You cannot use staging to delete or deactivate collections. For more information on manually deactivating collections, see Delete a Member or Collection (Master Data Services).

Moving explicit hierarchy members

When you move the location of members in explicit hierarchies in bulk, you can designate the following.

  • A consolidated member as a parent of a consolidated member.

  • A consolidated member as a parent of a leaf member.

  • A leaf member as a sibling of a leaf or consolidated member.

  • A consolidated member as a sibling of a leaf or consolidated member.

Staging Tables and Stored Procedures

The [!INCLUDEssMDSshort] database includes the following types of staging tables that you can populate with your data.

For each entity in the model, there is a staging table. The table name indicates the corresponding entity, and the entity type such as leaf member. The following image shows the staging tables for the currency, customer, and product entities.

Staging Tables in MDS database

The name of the 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.

The [!INCLUDEssMDSshort] includes the following types of staging stored procedures.

  • stg.udp_<name>_Leaf

  • stg.udp_<name>_Consolidated

  • stg.udp_<name>_Relationship

For each entity in the model, there are three stored procedures that correspond to the leaf member, consolidated member, and relationship staging tables. The following image shows the staging stored procedures for the currency, customer, and product entities.

Staging Stored Procedures in MDS database

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

Logging Transactions

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 using [!INCLUDEssMDSmdm], no logging occurs.

In [!INCLUDEssMDScfgmgr], the Log staging transactions setting does not apply to this method of staging data.

Related Content