SQL Doc fails to identify inter database dependencies

cfpatcfpat Posts: 5
edited December 5, 2014 8:37PM in SQL Doc
SQL Doc identifies intra database dependencies, but fails to identify the cross database dependencies. Tables used in views, tables used in SPs, etc... nothing comes through.
I am using 3.0.3.9.

Could swear that I was able to see those using a prior version when evaluating the product.

Any suggestion?
· Share on Twitter

Comments

  • Rob CRob C Posts: 419 Gold 2
    Hi,

    Are you launching SQL Doc by right clicking a database in SSMS and choosing the "Document [database]..." option? If so, then try launching SQL Doc independently via the Start menu in Windows. There is a bug in this version of SQL Doc that causes it to give incorrect dependency information when it is launched from the menu within SSMS.
    Software Engineer
    Redgate Software
    · Share on Twitter
  • cfpatcfpat Posts: 5
    Robert,

    Thank you for your answer. I have tried using SQL Doc from the Win Start menu, with the same results.

    What is troublesome is that I have generated documentation during the selection process that identified the inter database dependencies properly. I have persisted that documentation and can definitely see that it was accurate. It fails to replicate that proper behavior now, no matter how I access the SQL Doc app.

    I'm using 3.0.3.9, the latest version, and the inability to retrieve inter database dependencies manifests against SQL 2008 R2 and SQL 2014 servers alike.
    · Share on Twitter
  • Rob CRob C Posts: 419 Gold 2
    Would you be able to send me the create scripts for some of the problematic objects? If I can get a script for one of the objects in the main database and scripts for the things it references in the other database then that would help me replicate the behaviour you are experiencing.

    Email them to support@red-gate.com and put #32849 in the subject line.

    Thanks!
    Software Engineer
    Redgate Software
    · Share on Twitter
  • cfpatcfpat Posts: 5
    Robert,

    Thank you for your answer. Rather than giving you scripts of current production objects, this gave me an troubleshooting idea.
    I will create a couple of test databases and cross db references with simple objects. If SQL Doc fails to identify dependencies, I will then be able to give you something fairly clean and straight forward.

    Thanks for the suggestion, I should have thought of doing that myself first and we can take it from there. I hope this fails, BTW :) the alternative would be unpalatable.
    · Share on Twitter
  • Rob CRob C Posts: 419 Gold 2
    OK, I look forward to hearing the results :)
    Software Engineer
    Redgate Software
    · Share on Twitter
  • cfpatcfpat Posts: 5
    Robert,

    I sent you an email with scripts and screen shots.

    My observations are that the SQL DOC UI will identify and show the intra db dependencies properly, but will NOT show the inter database dependencies.
    However, without any other input but clicking on "Generate documentation...", the resulting documentation WILL show both inter and intra db dependencies.
    · Share on Twitter
  • david.youdavid.you Posts: 13 Bronze 1
    Hi Christophe,

    The behavior you're seeing is a known bug within our system (SDOC-1646). A possible workaround that seems to work for some customers is to launch the tool from the standalone executable instead of from SSMS.

    At this point, there's no timeline as to when this bug will be fixed. Please let us know if you have further questions or concerns.

    Best,
    David
    · Share on Twitter
Sign In or Register to comment.