How do I set up DbUp for a SQL Server database in .NET Core?

Install the DbUp-SqlServer NuGet package, configure a connection string, and add your SQL scripts to a folder. DbUp will automatically run unexecuted scripts and track them in a journal table upon application startup or deployment.

DbUp vs Entity Framework Core migrations: which is better?

DbUp is better for teams who prefer raw SQL control and simplicity, while EF Core migrations integrate closely with code-first models. Choose DbUp for direct SQL management; EF Core for ORM-based workflows.

Can DbUp handle rollback of database changes?

No, DbUp does not support automatic rollbacks. You must write custom SQL scripts for reverting changes or rely on database backups, making it less suitable for environments where rollbacks are frequent.

How does DbUp track which scripts have been run?

DbUp creates a table (default name SchemaVersions) in your database that stores metadata like script names and execution timestamps. It checks this table before running new scripts to avoid duplicates.

Is DbUp good for microservices with multiple databases?

Yes, DbUp's multi-database support and lightweight nature make it suitable for microservices, but each service must manage its own migrations independently, which can lead to coordination challenges.

What are the limitations of DbUp compared to FluentMigrator?

DbUp is simpler and SQL-focused, while FluentMigrator offers a fluent API for code-based migrations with more built-in features like versioning. DbUp requires more manual SQL work but is easier to start with.

Open-Awesome

DbUp

MITC#6.1.1

A .NET library for deploying and versioning SQL database changes across multiple database systems.

Visit Website GitHub

2.6k stars537 forks0 contributors

What is DbUp?

DbUp is a .NET library that automates the deployment of SQL database changes. It solves the problem of managing database schema versions by tracking executed SQL scripts and applying only the necessary updates to keep databases synchronized with application code. This ensures consistent and reliable database migrations across development, testing, and production environments.

Target Audience

.NET developers and DevOps engineers who need a lightweight, code-integrated solution for managing database migrations in SQL Server, PostgreSQL, MySQL, and other supported databases.

Value Proposition

Developers choose DbUp for its simplicity, minimal configuration, and seamless integration into .NET applications. Unlike heavier migration frameworks, it focuses solely on script execution and tracking, offering a reliable and straightforward approach to database versioning.

Overview

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 database up to date.

Use Cases

Best For

Automating SQL script execution in .NET application deployments
Managing database schema changes across multiple environments (dev, test, prod)
Versioning databases for SQL Server, PostgreSQL, or MySQL projects
Integrating database migrations into CI/CD pipelines
Ensuring consistent database states for .NET microservices
Tracking and auditing SQL change history in a journal table

Not Ideal For

Teams using Entity Framework Core or similar ORMs that prefer code-first migrations over managing raw SQL scripts
Projects requiring built-in rollback mechanisms or complex data transformation features, as DbUp focuses on forward-only migrations
Organizations needing commercial support or guaranteed SLAs, since DbUp is community-maintained with varied extension support
Environments where database changes are tightly integrated with application logic in a single framework, as DbUp operates independently

Pros & Cons

Pros

Multi-Database Compatibility

Works with SQL Server, MySQL, PostgreSQL, SQLite, Oracle, Firebird, and Redshift through dedicated NuGet packages, as shown in the detailed status table, ensuring broad support.

Minimal Configuration

Designed for simple integration into .NET apps, build scripts, or CI/CD pipelines with a code-first approach, reducing setup overhead.

Reliable Script Tracking

Maintains a journal table to record executed SQL scripts, preventing duplicate runs and ensuring consistent database states across deployments.

Extensible via Community

Community projects like DbUpX offer enhancements such as content hashing, script ordering, and Liquibase changelog support, though support varies.

Cons

No Built-in Rollback

DbUp lacks automatic rollback capabilities for failed migrations; handling errors requires manual intervention or custom logic, which can be risky in production.

Community Extension Dependency

Advanced features like hashing or Liquibase support rely on community-maintained extensions, which may have inconsistent updates or documentation, as noted in the README.

Limited Native Script Management

Basic script ordering and dependency management are not natively supported; complex scenarios require extensions or custom code, adding complexity.

Frequently Asked Questions

Related Projects

FluentMigrator

Fluent migrations framework for .NET

Stars3,502

Forks701

Last commit8 hours ago

EFCorePowerTools

Entity Framework Core Power Tools - reverse engineering, migrations and model visualization in Visual Studio & CLI

Stars2,508

Forks336

Last commit3 days ago

roundhouse

RoundhousE is a Database Migration Utility for .NET using sql files and versioning based on source control

Stars916

Forks244

Last commit2 years ago

Evolve

Database migration tool for .NET and .NET Core projects. Inspired by Flyway.

Stars905

Forks119

Last commit9 months ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub