Activity overview
Latest activity by robnikkel
Hi Andy,
That's what I suspected. So, we've decided to workaround this issue using static data linking, but it is not ideal. Here's our proposed solution:
Each dev would have two databases linked to our DB in source control. One for developing our software and mucking around with the database. The other for committing schema, and static data changes. We would never commit anything through the first DB, but rather use the "Get Latest" periodically to reset the DB state to what's in source control. The latter would be used to commit schema/data changes as desired and would essentially serve as a master copy of our source-controlled DB.
I think this will work for us, but it's a bit annoying. Hopefully you will have some improvements in the software down the road to manage data a bit better. If you can think of a better workflow, I'm all ears.
Thanks,
Rob / comments
Hi Andy,
That's what I suspected. So, we've decided to workaround this issue using static data linking, but it is not ideal. Here's our proposed solution:
Each dev would have two databases linked...
Eddie,
I appreciate the link, but I've already played with the tool, and was hoping for some more advanced features for excluding/including schema. For example, regular expressions, or even the ability to manually decide whether a table is source controlled or not (check list). In the time being, we're going to have to change our DB to create dynamic tables in a schema we don't want source controlled and then put a filter to exclude tables contained in it.
Regards,
Rob / comments
Eddie,
I appreciate the link, but I've already played with the tool, and was hoping for some more advanced features for excluding/including schema. For example, regular expressions, or even the ab...
Dynamic vs Static Data in source control
With our application DB, we have a number of required data rows to run the product, however, the data is dynamic in nature. In other words, it's not "lookup" data that does not change. This data ...
Choosing which Tables to add to source control
I'm new to SQL Source Control, but I currently haven't found any way to manually select which tables I actually want to source control. Looks like the only thing I can play with in terms of decidi...