Preventing multiple Assembly includes

steven Evans · February 16, 2019 11:33AM

We have been working with the excellent redgate tools for many years. We uses SQL Source Control (V6.1.8) with TFS to track Database changes and use SQL Compare (v13.7) and SQL Data Compare to produce update scripts.

We have hit a small issue, we are adding a Assembly to our next version. During development updated the Assembly after some other Database changes where made. Now when we compare an old db with the current source control version we get the Assembly included twice (i assume the original and the update version) at different points in the updates script. Is there a way to only have the current version included?

Sergio R · February 19, 2019 7:50PM

This is probably caused by migration scripts: when you create a migration script, SQL Source Control captures the state of any dependent objects. The "old" assembly is probably being created because of that.

steven Evans · February 20, 2019 11:23AM

So if I where to "edit & save" the dependant scripted would that help?

Sergio R · February 26, 2019 3:53PM

In theory yes, however in practice we have seen that some times dependency changes aren't picked correctly when a script is edited.
If you don't need any of the migration scripts anymore, you can quickly resolve this by just emptying the "Custom Scripts" subfolder in your repository (however please note that you can't individual migration scripts this way: it's all or nothing).

Preventing multiple Assembly includes

Answers

Product Learning

Community Forums

Events & Friends

Simple Talk