Skip to content

GettingStarted

Jump to bottom Edit New page
Rob Reynolds edited this page Jun 10, 2011 · 18 revisions

#Getting Started

##Introduction Welcome to RoundhousE (RH)! RH is one of the most intelligent database change management (also known as migration framework) OSS tools out there. Over the next couple of chapters you are going to learn how to effectively use RoundhousE to solve the complex business problem of managing change for your database. You will see that RH makes it really easy and as you learn the tool, you will wonder how you ever used anything else.

##Prerequisites ###Database Installed Whatever database you are going to use, be it SQL Server or be it MySQL, needs to be installed so you can do database change management.
###.NET Framework 3.5
You will also need to have the .NET framework installed. Currently RH uses 3.5.
###Other Prerequisites The install agent (usually a person running rh) needs to be able to create databases on the database (which usually means SA).

##Run the Sample for Familiarization If you've downloaded the application, the best way to see the power of RoundhousE is to actually run the sample. It will also help you familiarize yourself with how RoundhousE works.
###Sample Prerequisites The sample is run against SQL Server 2005/2008 (and it works with express as well), so you would need that installed. You can also attempt to run the sample against other database types. ###Running It

  1. Go to code_drop/sample (if you have the source) or to sample if you downloaded the release. Go into the deployment folder.
    sample folder has deployment
    Pick one

  2. Run LOCAL.DBDeployment.bat.
    Information Stage

  3. Press {Enter}. Notice all of the things it does. It just created our database, versioned it, then applied all of the database scripts (marking them as part of this version). Then it saved the output of what it ran to a folder.
    RH Run Log Part 1
    RH Run Log Part 2

###Roundhouse Change Drop Folder Notice how it ended telling us there was a folder where it put all of the changes it made. Let’s head there.
Below is the output folder. The structure of the output folder is databasename\server\yyyyMMdd_HHmmss_ffff.

Roundhouse Output Folder The convention here is the common application data folder on a machine followed by RoundhousE. Then we have a folder for the particular database followed by the instance. The actual folder we drop the changes into are YYYYMMDD_HHmmss_fractions. Hence the one in the picture was run on 06/07/2011 at 21:54:37 with so many fractions of a second.
In the folder we see two things:
Run Output Folder contains items it ran and the change log

Anyone can edit this

Add a custom sidebar
Clone this wiki locally