title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic |
---|---|---|---|---|---|---|---|
Staging Stored Procedure |
Use one of three stored procedures to initiate the staging process from SQL Server Management Studio in Master Data Services. |
CordeliaGrey |
jiwang6 |
04/01/2016 |
sql |
master-data-services |
conceptual |
[!INCLUDE SQL Server - Windows only ASDBMI]
When initiating the staging process from [!INCLUDEssManStudioFull], you use one of three stored procedures.
-
stg.udp_<name>_Leaf
-
stg.udp_<name>_Consolidated
-
stg.udp_<name>_Relationship
Where name is the name of the staging table that was specified when the entity was created.
The following table lists the parameters of these stored procedures.
Parameter | Description |
---|---|
VersionName Required |
The name of the version. This may or may not be case-sensitive, depending on your [!INCLUDEssNoVersion] collation setting. |
LogFlag Required |
Determines whether transactions are logged during the staging process. Possible values are: 0: Do not log transactions. 1: Log transactions. For more information about transactions, see Transactions (Master Data Services). |
BatchTag Required, except by web service |
The BatchTag value as specified in the staging table. |
Batch_ID Required by web service only |
The Batch_ID value as specified in the staging table. |
User Name | Optional parameter |
User ID | Optional parameter |
The following example shows how to start the staging process by using the staging stored procedure.
USE [DATABASE_NAME]
GO
EXEC[stg].[udp_name_Leaf]
@VersionName = N'VERSION_1',
@LogFlag = 1,
@BatchTag = N'batch1'
@UserName=N'domain\user'
GO
Validation Stored Procedure (Master Data Services)
View Errors that Occur During Staging (Master Data Services)