Custom migration scripts causing build fails

Hello,

We are using SQL SourceControl, DLM Automation tools and TeamCity. When we add migration script under Custom Script directory. DLM Automation Build starts complaining about existing schema, however migration scripts doesn't have anything to do with that schema. The migration script doesn't create any schema it just drops some indexes, change fields size and recreate indexes.

Another thing worth mentioning is that the schema doesn't belong to the database. It is a synonym to another database.

It looks like as soon as we add custom scripts it stops working.

Does DLM Automation support migration scripts? How to stop it from going to another database and creating duplicate schema?

Comments

Sign In or Register to comment.