Strategy for applications that have config data in the db

Early Access Program for SQL Source Control

Moderators: Chris Auckland, David Atkinson, sherr

Strategy for applications that have config data in the db

Postby neilx » Thu Jun 03, 2010 12:30 pm

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).
Posts: 8
Joined: Fri Apr 20, 2007 9:08 am

Postby David Atkinson » Thu Jun 03, 2010 1:12 pm

The only advice I can give you is to try it and let us know if you come across any hurdles. If you have config data that you want to store alongside your source controlled schema, you can achieve this using SQL Data Compare Pro. This is described here:

Source control static data using SQL Data Compare Pro

Deployment is achieved using a combination of SQL Compare Pro and SQL Data Compare Pro, or you can build it into your build process.

Automate your database builds using SQL Compare Pro and SQL Data Compare Pro

If you hit any issues, we'll be happy to discuss these with you. What you describe is exactly the problem we are attempting to solve in this tool.

Kind regards,

David Atkinson
Product Manager
David Atkinson
Posts: 1124
Joined: Mon Dec 05, 2005 4:54 pm
Location: Twitter: @dtabase

Return to SQL Source Control EAP

Who is online

Users browsing this forum: No registered users and 0 guests