• Since you started a new thread and Chris pointed me back to this one I will post here.

    I would agree that trying to keep this data in multiple tables is very bad design decision. It will cause you nothing but grief and anguish. You will need to implement triggers in each of the tables in order to even have a chance at making this work.

    Lowell asked if you are certain that the rows always exist in all tables or if there is a possibility that you will have to create them. I never saw an answer from you on that.

    Personally I would run away from this design as quickly as possible. Normalize your data and keep one and only copy of the details. There are a number of people on this thread already who can and will help you normalize your structures but you are going to have to provide some details. By details I don't mean another description of the issue, I mean actual ddl, sample data and a bit more detail about these web pages.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/