Bug - Dependency shown that does not exist

Ran compare to update a stored procedure from our dev to test environment and it shows a dependency for table that isn't even used in the stored procedure. See attached screen print.

Chris Kowitz


  • Hi - apologies for the lack of information in this part of the UI. We have some long-term plans to try and improve the dependency logic in SQL Compare to display more information about why certain dependencies have been selected (and to allow for more fine-grained control over dependencies) but we don't have anything concrete yet and it may be a long time before we're able to work on it.

    However, in the meantime, it might be helpful if you could post the creation scripts for the objects involved - maybe we can help figure out why a dependency has been suggested here (or reproduce the bug if it turns out to be completely erroneous). If you want to keep your database details private you can get in touch with [email protected] who can help figure out a reproduction

    Hope that's helpful,
Sign In or Register to comment.