--
You received this message because you are subscribed to the Google Groups "DbUp Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dbup-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Agreed we use octopus deploy with great success. If you didn't want to do that you could just create a powershell script to wrap your console app and use a hashtable of your connection strings to loop through them passing each connection string to your dbup app as a command line argument.
On Monday, July 14, 2014, Stephen Krauklis <stephen...@gmail.com> wrote:
Dale,--Check out Octopus Deploy. There is an article on the concept here: http://octopusdeploy.com/blog/howto/deploy-a-sql-databaseWe use this tool with DbUp to deploy database changes to numerous 'environments'.Stephen
On Friday, June 27, 2014 7:06:27 AM UTC+10, Dale Janssen wrote:I have been working with DbUp and can see how to deploy a Database update/script to a single Database. But I have a situation where I need to deploy the same script to a dozen or more identical Databases - all named uniquely, some on the same server, some on others, but all accessible via a connection string.Can you suggest the best way to accomplish this?I could put together a web.config transform with a custom .target file, so it is easy to see how to create multiple customized app.configs with different connection strings and then have the console program loop through all app.config files found - but that sure seems like the long way around.Any other suggestions?
You received this message because you are subscribed to the Google Groups "DbUp Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dbup-discuss+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.