Two-way sync: how to import in a Database Project a table, AFTER Import Schema?
Hello everybody,
consider this scenario: I import a schema in a Database Project, then I create a table IN SQL SERVER, and I want to sync it with project.
The only way I've architected till now is to create the table, script it, delete table in SQL Server, and copy the script in Database Project (deleting "if exists drop", because this syntax is unsupported in Team Edition for Database Professionals).
More practical ways?
[456 byte] By [
paolod] at [2008-2-12]
With our current CTP, we only support one-time schema importation. However, we are looking to support incremental schema import by our RTM release. This means if an extra table exists in the live datase, you will be able to import just the new table into your database project.
However, I would encourage you to make all your schema changes from the database project. So in this scenario, instead of creating the table in the live database, you can add the table directly to the database project and use our update build/deployment to push out just the new table to the database.
Thanks!
-Jon
