Managing Cross-Database Dependencies in Builds (Redgate video)

Building your database code is an essential practice to ensure that it compiles from source and that dependencies are met. But things can get tricky when you have objects in some databases which is dependent upon objects in other databases — or even circular dependencies.

In this 20 minute video, I give an overview of the two most popular options that Redgate customers use to manage cross-database dependencies when building SQL Server databases with Redgate’s SQL Change Automation.

3 Comments. Leave new

  • Alex Friedman
    July 29, 2019 6:57 am

    I realize this is a Red Gate centric post, but how would you handle circular dependencies with SSDT? Thanks!

    • Dangit, I responded to this and somehow didn’t submit it, I think. Trying again!

      I don’t know of any magic for circular dependencies in SSDT. The only way I know is to move some of the objects out into a separate project(s), thereby making the dependencies one way instead of circular. There are a few folks who have described this, if you search on “SSDT Circular Dependencies” they are the top posts, so guessing you’ve seen them before.

      • Alex Friedman
        July 30, 2019 12:58 am

        Yup, separating objects, or using dacpacs. For dozens of databases with thousands of frequently changing objects, however, this quickly becomes unmanageable. As a result, currently we only use SSDT for newer, self-contained projects that live in a single schema. I really wish there was a better solution for DBs with circular dependencies.


Share a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: