SQL Source Control has been working really welll for me so far on my main database.
I wonder if you have any advice on a strategy for versioning a website that stores essential config settings in a dedicated database? I am using Dotnetnuke (DNN).
In order to check out a working current version of a DNN site, I need the files and db schema (no problem) plus the data in the tables that drive the site (aspmembership, tabs, modules, portals etc).
It would be really good to check out an svn project for the latest version of the site then build it locally (I would need to create an ms-build script), make changes then commit and deploy to the production site automatically (with CI).