January 14, 2011 at 1:56 am
Is anybody out there using DBPro for database (schema and data) source/version control, particularly within an Agile development methodology? If so, how did you go about it, what problems have you had to overcome and would you recommend DBPro as being the tool of choice in this scenario?
Thanks
Lempster
January 14, 2011 at 7:58 am
Yep, I've done it. It can work great. It requires a lot of discipline, but you can do it. I've written a couple[/url] of articles[/url] on it (although they're a little long in the tooth at this point) that should help a bit. I think there might be a post or two on my blog as well.
The hardest part is getting everyone to agree that all deployments of all database objects have to come out of source control. The developers, usually, get on board quickly. It's everyone else, DBAs, testers, management, that have issues with this. The other trick is picking a method for setting up security. I show how you can do this using compound projects, but I've found when your projects get really big, or the number of environments gets to be more then three or four, this approach breaks down. A more resilient method is to use post deployment scripts with big IF statements to deploy different security for different environments.
Other than that, you can automate the entire thing.
An alternate choice these days, is Red Gate's SQL Source Control.
I wrote about both in the Red Gate Team Development book[/url]. It might be worth a read.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 14, 2011 at 8:15 am
Thanks for the reply Grant. You are right, this is development led and the issue will be trying to bring everyone else on board. I'll have a read of your articles....
Regards
Lempster
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply