Hello, and welcome to this short video in which we’ll see how ER/Studio Data Architect can help us easily move changes that we’ve made in our physical data models to the database that they represent.
Here I have a physical data model for SQL Server 2005. Let’s go make a change to this Broker Table > Add a New Column > Broker Preferred Name, then we’ll add this to the location we prefer in the table > Click OK. Now we want to push that column into a database by comparing the model to the database using the Compare and Merge Utility. We’ll compare the model directly to the database, therefore we’ll log into the database. We want to make sure that the correct settings are set here (in the dropdown menu list) like comparing tables and columns, and then we’ll run the comparison.
We can see that the differences here are that the new column does not exist in the database table, and there are some sequences orders that are off now. So let’s change the resolution from Ignore to Merge into Target. We’ll create an ALTER script to push this change. We’ll store the ALTER script here but we will also load it into an iSQL facility that’s provided with Data Architect, where we can go ahead and connect to the data source with an ODBC driver and execute it. That’s it!
We’ve easily moved that change down from our model to our database.
Topics : Data Modeling,
Products : ER/Studio Data Architect,