Recommended setup for Red-Gate SQL Source Control
My setup is that we have one â€œnearlyâ€ core database that gets replicated for each client. This core is probably 90% of the objects. There is then the 10% that are client specific. For example there may be a View that filters on different names for different clients, there is a user that is unique for each client database (but linked to a standard role).
At the moment I have each client database linked to the same TFS project (in dedicated model). If there is a bug found I fix it in one client database and check-in. Then I get latest for all of the other client databases. I have to be careful when getting latest not to get objects that are different for each client (there is a generic version of each object in TFS which I use initially, but once Iâ€™ve configured the database for the client I donâ€™t want to overwrite the database version with the one from TFS). I also have to be careful when committing changes as I donâ€™t want to overwrite the generic version with the client specific version.
Iâ€™m sure this kind of setup isnâ€™t unique â€“ how are other people handling this? Any advice is much appreciated. (Iâ€™ve posted this question on http://ask.sqlservercentral.com as well)