Home Forums SQL Server 2008 SQL Server 2008 - General Check Constraint Question - Situations Where a Child Record Should Be Limited to One Occurrance RE: Check Constraint Question - Situations Where a Child Record Should Be Limited to One Occurrance

  • It is possible and it works. I did this at a previous employer where I separated information into two separate tables. The idea was to allow for future expansion where a one to many relationship would be permitted, but currently was not. I wanted the tables in place during initial design rather than having to create the new table later when he new functionality would be implemented.

    Doing the initial work upfront was to make it easier, though it never became a requirement. In fact, this particular system actually went away in favor of a third party solution.