You can use Deploy Clone to deploy structure only, or structure data.
Keeps the unique identifier (MUID) consistent between environments, which is necessary if you want to keep models in sync between Dev and Prod.
If you want the version added to the name, edit the database name at the beginning of the script.
The oltp script drops an existing Adventure Works database, and the data warehouse script drops an existing Adventure Works DW.
This can deploy structure changes only (ex: a new column), or structure data (ex: refreshing Dev from Prod occasionally).Will only work when the unique identifier (MUID) is the same between source and destination.Not used that frequently; only appropriate for creating a brand new model using another model as a starting point.Before you do any deployments, you need to know the Service Name(s), especially if you have more than one MDS instance running on the same server.In most cases this is MDS1 if you only have one MDS web app & one MDS database running on the SQL Server instance.
Remote Desktop into source server where MDS is installed (ex: Dev). Locate the deployment package on a file share (this saves you from copying and pasting it from one server's configuration folder to the other).