Is there a tool out there that checks for Circular references

  • I was wondering if there is a tool that I can purchase that will find Circular references in my database?

    Although I thought I new what a Circular reference was, apparently I do not (I was using LINQ today and it told me that I had Circular references on more then one table). Can anyone give me a simple definition for Circular references so I can avoid this problem in the future?

    Thanks

  • The Red Gate database documentation tool, SQL Doc, will do it I think.

    The problem is, it's really easy to get a circular reference. All you need is a set of FK's between tables that loops.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Grant Fritchey (10/29/2009)


    The Red Gate database documentation tool, SQL Doc, will do it I think.

    The problem is, it's really easy to get a circular reference. All you need is a set of FK's between tables that loops.

    Thanks so much for the information. I will purchase the product.

    I have a really dumb question. The system that I am working on apparently has a few circular references that up until I tried to use Linq, never caused any problems. Circular references sound real bad, but are they?

  • meichner (10/29/2009)


    Grant Fritchey (10/29/2009)


    The Red Gate database documentation tool, SQL Doc, will do it I think.

    The problem is, it's really easy to get a circular reference. All you need is a set of FK's between tables that loops.

    Thanks so much for the information. I will purchase the product.

    I have a really dumb question. The system that I am working on apparently has a few circular references that up until I tried to use Linq, never caused any problems. Circular references sound real bad, but are they?

    Not necessarily. It's usually an indication of some design issues that might indicate a bad design, but they won't necessarily cause you any problems at all normally. It's just when you get into using an automation tool that can walk the dependency try that you'll see problems.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Grant Fritchey (10/29/2009)


    meichner (10/29/2009)


    Grant Fritchey (10/29/2009)


    The Red Gate database documentation tool, SQL Doc, will do it I think.

    The problem is, it's really easy to get a circular reference. All you need is a set of FK's between tables that loops.

    Thanks so much for the information. I will purchase the product.

    I have a really dumb question. The system that I am working on apparently has a few circular references that up until I tried to use Linq, never caused any problems. Circular references sound real bad, but are they?

    Not necessarily. It's usually an indication of some design issues that might indicate a bad design, but they won't necessarily cause you any problems at all normally. It's just when you get into using an automation tool that can walk the dependency try that you'll see problems.

    Thanks so much for the help. I really appreciate it.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply