Master data services deployment

Question

What is the best approach to keep Production,dev and test enviroments in sync?

We have Master Data Services database in our development, Test and Production environments. Data is been entered into Production and we need to keep our test and development servers in Sync. I couldn't find the documentation to handle this.

I am not sure if this process is correct-

For moving updated data from Development we are following this process-

create second version of the model and make the changes in it and then deploy the 2nd version to test and prod.

Can we do this same above process from Production to test and Development to keep them in Sync?

Thanks

Answer 1

Two options come to mind:

---

• Snapshot replication

Snapshot replication distributes data exactly as it appears at a specific moment in time and does not monitor for updates to the data. When synchronization occurs, the entire snapshot is generated and sent to Subscribers.

---

• Log shipping

SQL Server Log shipping allows you to automatically send transaction log backups from a primary database on a primary server instance to one or more secondary databases on separate secondary server instances. The transaction log backups are applied to each of the secondary databases individually.

Answer 2

MDS has tool which is called MDSModelDeploy. You can create package with all business rules, schema and data. Ship it over to some other machine and.

• clone model (preserving keys, etc)
• update model

More information here