Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Staging Stored Procedure (Master Data Services)

Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).

When initiating the staging process from SQL Server Management Studio, 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 SQL Server 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

Staging Process Stored Procedure Example

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

Community Additions

ADD
Show:
© 2015 Microsoft