Projects

MigratorDotNet

Database migrations for .NET. Based on the idea of Rails ActiveRecord Migrations.

RoundhousE DB Migrations

RoundhousE is an automated database deployment (change management) system that allows you to use your current idioms and gain much more. Currently it only supports Microsoft SQL Server, but there are future plans for other databases. It seeks to solve both maintenance concerns and ease of ... [More] deployment. We follow some of the same idioms as other database management systems (SQL scripts), but we are different in that we think about future maintenance concerns. We want to always apply certain scripts (anything stateless like functions, views, stored procedures, and permissions), so we don’t have to throw everything into our change scripts. This seeks to solves future source control concerns. How sweet is it when you can version the database according to your current source control version? [Less]

schambers's fluentmigrator

Fluent Migrations framework for .net

fluentmigrator

Note that the source for this project has been moved to GitHub - http://github.com/enkari/fluentmigrator/ This is a rewrite/fork of the popular Migrator.Net project. We wanted to re-work large portions of the code without breaking backwards compatibility on Migrator. As a result we decided to fork ... [More] the project to take more of a fluent approach to creating migrations. [Less]

octalforty-wizardby

Pretty much inspired by Ruby on Rails' Migrations, octalforty Wizardby is a powerful yet easy to use database migration framework primarily targeting .NET. octalforty Wizardby allows you to write migrations using concise, DRY, platform-independent and human-readable DSL; it also tracks which ... [More] migrations were applied to a particular instance of a database and automatically upgrades database schema. It also generates downgrade scripts, so you can always revert your database schema to an arbitrary version. [Less]

Phinx

PHP Database Migrations for Everyone

mp

MP is a generic migrations architecture for managing migrations between versions of a web application. It can be used to migration database schemas as well as perform arbitary code during upgrades and downgrades. MP includes a command-line utility that makes it easy to run migrations. MP also ... [More] has a PHP API for easy integration into existing frameworks or ORM tools. If you are looking for a lightweight, flexible, and easy-to-use utility to help you manage application and database versioning, MP is for you. [Less]

ruckusing

Ruckusing Migrations is a "Database Migrations" framework for PHP5. The framework is modeled after the migrations package as party of Ruby on Rails's ActiveRecord.

rikmigrations

RikMigrations is a database migration library for .NET based on the migrations facility provided by Ruby on Rails. It allows simple upgrading and downgrading of databases using .NET code (such as VB or C#) either from the command line or built into your application. Unlike many other migration ... [More] frameworks, RikMigrations is a stand-alone library which does not rely on a large surrounding framework. More information can be found on the Project homepage - http://www.rikware.com/RikMigrations.html A number of tutorials are available from http://www.rikware.com/RikMigrations.html and more are being added regularly. Please be patient as the documentation is created. Development is being supported by my job, but documentation is not :s If you have specific questions drop a comment here or contact me via the contact page at http://www.rikware.com/contact.aspx. I will concentrate documentation efforts around people's requests. [Less]

mite-net

Inspired by Ruby on Rails migrations, written in C# & boo, Mite brings the versatile tool of database migrations to the .Net community. We've implemented migrations in a db agnostic style that makes sane assumptions when information is not provided. Static typing along with a fluent ... [More] interface makes writing migrations using Mite in any of the CLR .Net Languages a very pleasant experience. For those not familiar with migrations. Migrations offer a simple way to maintain the version of your db schema through convention. Which does away with managing Sql Scripts or manually managing the database and allows your code/build script to up or down the database to the appropriate schema version for your application. An example migration: company = "Company" employee = "Employee" up: add_table company: string "Name", { max_length = 65, unique = true } add_table employee: string "Name", { max_length = 65 } int32 "CompanyId" add_relation "employment", Cardinality.OneToMany, company, employee + ".CompanyId" down: drop_table employee drop_table company Or in C# ... public class Migration1 : MigrationBase { public Migration1(IAdapter adapter, string databaseName) : base(adapter, databaseName) { } public override uint Version { get { return 1; } } protected override void Up() { AddTable("activity_participation", new Int32("registration_id", false), new Int32("activity_id", false) ); } protected override void Down() { DropTable("activity_participation"); } }Unless overridden, all tables by default receive a primary key called "Id" that is a 32-bit integer that autoincrements if the DB supports it. Two local variables are used: company and employee. This is about keeping it DRY. Since the boo based DSL is actually a language, using language features like these local variables and the use of the Cardinality enumeration are possible. Many of the methods in Mite have smarts. The add_relation method, for example, does not need you to tell it that you want to relate employee.CompanyId to Company.Id. It assumes that you are going to hook up to the primary key unless you otherwise specify. If you don't like the looks of the DSL, don't worry. Mite migrations can be written in plain old C# as well. Also, the boo can be written with C# naming conventions instead of the ruby-like ones shown above. The same migration from above could also be written as the following. company = "Company" employee = "Employee" Up: AddTable company: String "Name", { max_length = 65, unique = true } AddTable employee: String "Name", { max_length = 65 } Int32 "CompanyId" AddRelation "employment", Cardinality.OneToMany, company Down: DropTable employee DropTable company For more information. Subscribe to Nathan's blog here. http://nathan.whiteboard-it.com/ [Less]