Dubnium Documentation
Welcome to Dubnium - a powerful database versioning and migration tool for SQL Server that provides automated database builds with comprehensive versioning capabilities.
What is Dubnium?
Dubnium is a .NET console application designed to solve the challenges of database version control and deployment. It enables development teams to:
- Version Control Database Changes: Track every database modification with sequential version numbers
- Automate Database Builds: Rebuild databases from scripts consistently across environments
- Manage Migration Scripts: Execute database changes in the correct order with proper error handling
- Compare Database Schemas: Identify differences between database versions and environments
- Support Continuous Integration: Integrate seamlessly with CI/CD pipelines for automated deployments
Key Features
Core Database Operations
- Migration System: Sequential script execution with version tracking
- Schema Management: Compare schemas between different environments
- Data Operations: Export table data to CSV files
- Environment Setup: Initialize and configure database environments
Command Categories
Dubnium organizes commands into logical categories:
- Information Commands: Version info, help, testing connections
- Project Commands: Initialize projects, setup environments
- Execution Commands: Build, deploy, compare, and manage database changes
- Verification Commands: Verify and validate operations
Getting Started
Installation
dotnet tool install --global dubnium-cli
Quick Start
-
Initialize a new project:
dbm init -
Configure your database connection in the generated
dubnium.ymlfile -
Setup the environment:
dbm setup -
Start managing your database changes!
Requirements
- .NET 8.0 or later
- SQL Server (2012 or later recommended)
- Windows, Linux, or macOS
Licensing
Dubnium offers both free and commercial features:
- Free Commands: Basic database operations, schema comparison, and migration management
- Paid Commands: Advanced features like automated builds and deployment require a commercial license
Commands requiring a license are clearly marked throughout this documentation.