Home Dashboard Directory Help
Search

Master Data Services 2012 deploy by James V Serra


Status: 

Closed
 as By Design Help for as By Design


1
0
Sign in
to vote
Type: Bug
ID: 762567
Opened: 9/13/2012 11:57:07 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

There seems to be a bug with MDSModelDeploy with the "deploynew" option: the MUID (the internal model ID in mdm.tblModel) from the source, which is stored in the package file when you create it, is not copied into the destinations mdm.tblModel when you use "deploynew". Instead, a new MUID is created, but the model name stays the same. This means you won't be able to later use MDSModelDeploy with the "deployupdate" option since the MUID's don't match. This bug does not happen if you use the model deployment wizard (it will use the same MUID from the source in the destination).

Note also that http://msdn.microsoft.com/en-us/library/ff486971.aspx is in error in saying the model deployment wizard will also copy the master data ("Master data is populated" under "Notes"), but it will not.

Also, on http://msdn.microsoft.com/en-us/library/hh479646.aspx and http://msdn.microsoft.com/en-us/library/hh479639 and http://msdn.microsoft.com/en-us/library/ff487019 and http://msdn.microsoft.com/en-us/library/ff486971.aspx, the spots where it says "model objects only" should really say "model objects/business rules/subscription views only", as the model deployment wizard deploys all three, not just model objects.
Details
Sign in to post a comment.
Posted by Microsoft on 10/2/2012 at 9:20 AM
Hi James,

We’re going to close this issue as “by design.” If you have any additional feedback to share please let us know.

Matthew
Posted by Microsoft on 9/25/2012 at 2:50 PM
Hi James,

I apologize for the mis-fire communication from last week. This may have been a team member replying to the wrong Connect issue, and the tool doesn’t support deleting comments once they’re entered.

We’ve been researching the behavior you’ve reported, and it if we understand your scenario correctly, you should be using the deployclone command line option and not the deploynew option. This will preserve the MUID from the source model. This video might provide additional information and assistance: http://msdn.microsoft.com/en-us/sqlserver/hh780972.aspx

Thanks as well for your feedback on the MSDN content. Our intent has been for the term “model objects” to include the things you mention (such as business rules) and not just entities, but there are opportunities to make the content more clear. We’ll work with the MSDN team to review the pages you identified.

Matthew
Posted by Microsoft on 9/18/2012 at 11:50 AM
As posted in the known issues, this is not expected to work at this time.
Sign in to post a workaround.