Question 1

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

Accepted Answer

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.

Question 2

DbUp vs Entity Framework Core migrations: which is better?

Accepted Answer

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.

Question 3

Can DbUp handle rollback of database changes?

Accepted Answer

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.

Question 4

How does DbUp track which scripts have been run?

Accepted Answer

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.

Question 5

Is DbUp good for microservices with multiple databases?

Accepted Answer

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.

Question 6

What are the limitations of DbUp compared to FluentMigrator?

Accepted Answer

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.

DbUp

What is DbUp?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions