What are the challenges you face when working across database platforms? Take the survey

How To Find Missing Dependencies

IanT8IanT8 Posts: 4
edited April 30, 2010 5:43AM in SQL Dependency Tracker
I've just used SQL Packager to package up a database and then install the package. The database creation process failed when it tried to create a view that depends on a table that dooes not exist.

I checked the original database, and indeed, the required table does not exist.

To my surprise, Dependency Tracker does not show dependencies that cannot be resolved.

Is there any way I can discover these broken dependencies using SQL Dependency Tracker or indeed any other method?



  • Options
    Unfortunately this isn't a feature of SQL Dependency Tracker.

    Finding invalid objects is going to be a feature of SQL Prompt 5, which will be out sometime this summer. I can put you on the beta notification list if you like, which means you'll be able to try an early version of the functionality.

    In the meantime, you'll have to do what you're doing. If you try to use SQL Compare (or SQL Packager) to deploy your schema to an empty database, it will fail due to these invalid objects. You can then fix them one by one. It's not ideal, but until we've added this feature to SQL Prompt, it's the best I can think of.

    David Atkinson
    Product Manager
    Red Gate Software
    David Atkinson
    Product Manager
    Redgate Software
Sign In or Register to comment.