But the barrier to entry for controlling an existing database is high. Roundhouse needs all the stored procedures, views, etc as files in a folder structure. Each script must be able to create or alter the entity. For teams supporting databases with thousands of procedures and views this work will stop evaluating Roundhouse. This is a shame as they are missing out on a superb tool. So I have created something to help get you started.
What does it do?My current client falls in to the category of having thousands of procedures and views which had to be scripted. So I created a tool to extract them from SQL Server.
Sql-baseline is run with three options; server name, database name and location for the files:
.\sqlbaseline.exe -s:"(local)" -d:AdventureWorks -o:C:\Db\Adventure
It will generate a script for all of the stored procedures and views and put them in the default Roundhouse folders:
\db \sprocs \viewsEach script is created with the Create if not Exists / Alter template which will check for the entity first and if it is missing create it. The files are then ready be run by Roundhouse.
I have a short list of updates which are coming soon
- Export functions and indexes
- Create all of the default Roundhouse folders
- New option to specify which entities to create
- Accept a set of custom folders