Develop and deploy databases in Visual Studio with migration scripts

Try ReadyRoll free for 28 days

Deploying and developing databases with ReadyRoll – a 2 minute intro

Want to work on databases in Visual Studio alongside your application? Feeling the pain of managing and deploying database changes manually? Then ReadyRoll's the tool for you.

It generates numerically ordered SQL migration scripts that sit inside your project and take your schema from one version to the next.

You can add them to version control, use them to build and release, and automate database and application deployments, all in one process.

Pricing information

per user

Buy now

Save up to 30% when you buy multiple licenses

Save time with automatic
migration scripts

Save time with ReadyRoll’s automatic suggestions for migration scripts. You can use them as they are, or edit them in Visual Studio before sharing them with your team.

The scripts are generated by the SQL Compare engine, the industry standard for comparing and deploying SQL Server database schemas quickly and accurately.

Get alerts when databases drift
Get alerts when databases drift

Keep full control over changes

Because you define your migration scripts up front, you keep precise control over how your changes are deployed. Scripts get a sequential number, and you add them to your version control system as part of your complete solution in Visual Studio.

Change management is simple and there’s no chance of errors from running scripts in the wrong order.

Deploy with confidence

Test scripts before they hit production with ReadyRoll’s shadow database. Use this disposable clone of your database to test your deployment and check your scripts take you to the state you want.

When you’re ready to deploy for real, you can be certain your changes work.

Get alerts when databases drift
Get alerts when databases drift

First class Visual Studio integration

ReadyRoll adds a new project type to Visual Studio. Your database changes live in the same solution as your application code.

Without leaving Visual Studio, you can pick up and edit scripts from other team members. The version control system you’re connected to via Visual Studio handles merging for you, and you can even kick off builds.

Supports build and release tools,
including Octopus Deploy

Trigger builds whenever you commit, and use the build artifacts to deploy changes to all your environments.

ReadyRoll also comes with built-in support for Octopus Deploy’s OctoPack. You can use Octopus variables in your scripts to configure how you deploy your changes to each environment.

Get alerts when databases drift
Get alerts when databases drift

Avoid "last one in wins" scenarios

Enable Programmable Objects in your project to source control stored procedures, triggers, views, and functions as individual T-SQL files.

This means when you and your colleagues make changes to these files, your usual version control system conflict resolution process applies. When a developer attempts to check in changes, they’ll always be prompted to incorporate other changes first, rather than overwriting them.

Helps with DevOps, team collaboration, and agility

ReadyRoll brings Dev and Ops together. It moves the review of changes into development, so bugs are caught early.

Developers and DBAs can join forces to apply and test fixes early on, when it’s still cheap.

How ReadyRoll works

1. Develop

Develop your database in Visual Studio or SQL Server Management Studio.

2. Sync

Use the ReadyRoll tool window in Visual Studio to preview and import schema and data changes.

3. Script

This adds a numbered SQL script to your project, which you can edit if you need.

4. Deploy

Check your project and scripts into source control, and deploy to your Dev/Test/Prod environments.

What our customers are saying

How to develop and deploy databases with ReadyRoll

This short video tutorial shows you how to start developing and deploying your databases with ReadyRoll SQL projects for Visual Studio, including:

  • Creating a new ReadyRoll database project in Visual Studio
  • Designing Tables and Views using SQL Server Data Tools in Visual Studio
  • Reverting unwanted changes and returning your database to a known "good" state
  • Deploying your database project to a remote SQL Server instance

Licensing FAQ

How many licenses will I need?

You’ll need one license for each developer using ReadyRoll. If your developers use more than one PC, let us know and we’ll set up your licenses accordingly (you won’t need to buy any extras, though).

Do build servers need to be licensed?

No – you don’t need a special license to perform unattended builds or deployments with tools like TeamCity, Team Foundation Server, Jenkins, or Octopus Deploy.

This gives you the flexibility to scale your DevOps capacity without incurring additional cost, and it means no messy software activation steps to run on your build agents.