> If tables, then if they are in the same DB, they should be in the same project. Lock-stepping two otherwise unrelated applications because they both share su

> If tables, then if they are in the same DB, they should be in the same project. Lock-stepping two otherwise unrelated applications because they both share support for a data structure is silly at best, and often impractical, especially if development for only one of the projects is "in-house". Consider the possibility that "A" is a commercial product produced by another company. Anyway, it's my experience most software upgrades don't involve a schema change, so it's worth optimising for the common case, and supporting the difficult case.