DbUp is a .NET library that helps you to deploy changes to SQL Server databases. It tracks which SQL scripts have been run already, and runs the change scripts that are needed to get your …

There are any number of other ways to use DbUp. Feel free to submit a pull request to update this section with more information. From PowerShell Another option is call DbUp directly from …

It has been copied to the DbUp docs so it is with the rest of the documentation and can be evolved over time. When I'm building an application that stores data, there are a few things I …

Warning: DbUp does not protect against Sql Injection attacks, code scripts allow you to generate an upgrade script dynamically based on data in your database if you need to.

By default, DbUp adds a table to your SQL Server database called SchemaVersions, which tracks the scripts that have already been executed. Before running, DbUp checks this table to work …

DBOps is a Powershell module based on DbUp that provides Continuous Integration/Continuous Deployment capabilities for SQL database deployments. It comes with an easy-to-use set of …

DbUp supports a number of different databases, the platforms are also listed under each database. Sql Server 2000 and later (any that is supported by Microsoft.Data.SqlClient)

With DBUp, by default every script will only be run once. The list of scripts ran on the database is kept in a table to ensure a script is never run again. There are cases where it makes sense to …

DbUp v3.0 added support for transactions. Not all changes can be rolled back, but for many DDL and data changes on databases other than MySql transactions work fine.

Philosophy Behind DbUp Usage Supported Databases FAQ Contributing DBOps Powershell Module More Info Schema Downgrading Script Providers Script Types Transactions Pre …