I created PoweruP to help me configure RoundhousE to manage a number of existing databases. This is not an easy task and can be a barrier which stops people trying out RoundhousE as is shown by this conversation
@dantup @monkeyonahill @davidfowl @jabbr and intro @keith_bloom's sql-baseline. github.com/chucknorris/sq… (FYI, name change pending) :D
— Rob Reynolds (@ferventcoder) July 19, 2012
This is a shame because once RoundhousE is setup it greatly increases development speed, it is simple to maintain and brings database development inline with application coding. What can stop people using it, is the need to extract all the stored procedures, views, functions, etc, from the database. With one command PoweruP will scaffold a new RoundhousE project from an existing database. Plus It will create the scripts and put them in the default RoundhousE folder structure. For a more detailed explanation see this post.
I am very pleased for PoweruP to be part of the Chuck Norris framework. I hope it will help more development teams to get started using RoundhousE because it is the best tool I have found for managing changes to the database schema.
2 comments:
Thanks for publishing this tool, it was very helpful!
I have a question for you.
Does PoweruP generate a dependency tree or deployment order?
Post a Comment