ReadyRoll 1

ReadyRoll 1.12 release notes

1.12.9 - March 2nd, 2016


  • Re-brand the product as Redgate ReadyRoll (Details)

1.12.8 - February 17th, 2016


  • Script Verification Helper (Details)

When using the DbSync tool to import a database, either the initial baseline or incremental changes, it is quite common to encounter failures at the verification stage. This is where ReadyRoll applies the generated script against the Shadow database, which it does in order to move the database version forward to match the project definition. For more information, see Target and shadow databases.

Problems often arise at this stage if the script that was generated by ReadyRoll causes SQL Server to throw an error. These errors often stem from:

  • Missing dependencies (e.g. a view that is missing a dependent view, a user that does not have a related login, a stored procedure that depends on a full-text index being present)
  • Invalid code in legacy objects (e.g. stored procedures that still use old style outer joins)
  • Syntax errors, resulting from user modifications to the generated script

Resolving the above errors may involve a number of different steps, depending on the cause of the issue.

To help you resolve these kinds of errors, we’ve added a new dialog within the ReadyRoll DbSync tool that appears when you encounter an error during the verification process.

This tool is displayed if an error occurs when you attempt to execute your script against the Shadow database. To resolve the issue, do one of the following:

  • Click Undo import to remove the generated script from your project and allow you to un-check any object(s) that may have caused the error

  • Click Open script to open the affected migration script and fix the syntax errors manually

  • Click Re-verify script to attempt to execute the script again; useful if you suspect that the underlying issue was temporal (e.g. a timeout error), or if you have subsequently fixed the issue through manual script changes

1.12.7 - February 5th, 2016


  • Full-Text Index script generation support (Details)
  • New Project Setting: Toggle Three-Part Object Reference object check on/off (Details)
  • New Project Setting: Group Programmable Object script files by schema (Details)


  • Deployment fails when migration “001” has transaction handling switched off (Details)
  • Unsupported programmable objects filter breaks when user enables “group by schema” (Details)
  • Reverting Data changes in the DbSync tool raises “Object reference not set” exception (Details)

1.12.6 - January 13th, 2016


  • Provide more context to SQL Server errors in DbSync tool (Details)


  • Some SQL Server error messages suppressed in DbSync tool (Details)

1.12.5 - December 24th, 2015


  • Text in DbSync tool difficult to read with Visual Studio dark theme (Details)
  • Error during Refresh in Offline Schema Model sync: Value cannot be null (Details)
  • Project setting DeployChangesImportSchemaFolders not working as expected (Details)

1.12.4 - December 7th, 2015


  • Improve programmable object setup process for new users (Details)


  • Build/Deploy process fails in VS2015 Update 1 (Details)
  • Cannot find SQLCMD.EXE when deploying in Visual Studio 2015 (Details)

1.12.3 - November 26th, 2015


  • Improve project setup process for new users (Details)
  • Allow trial license keys to be extended remotely (Details)


  • SQL Server passwords containing double-quotes cause “Failed to login” errors during deploy (Details)

1.12.2 - November 13th, 2015


  • Error during Import “Type is not marked as serializable”: A generic error occurs in the ReadyRoll DbSync tool-window when attempting to import changes from the target database into the Programmable Objects (Deploy-Changes) subfolders (Details)

1.12.1 - October 28th, 2015


  • Add Check for Updates menu item (Details)
  • Add menu links to make the documentation more accessible

1.12.0 - October 21st, 2015

Today’s release focuses on simplifying some key concepts within ReadyRoll.

In ReadyRoll 1.12, we've changed the terminology used in the product to make it easier to understand. 


  • Rename Deploy-Once Migrations to Migrations (Details)
  • Rename Deploy-Change Migrations to Programmable Objects (Details)
  • Define Additional Scripts separately to Programmable Objects (Details)
Old folder name (1.11 and earlier)New folder name (1.12 and later)
Deploy-Once MigrationsMigrations
Deploy-Change MigrationsProgrammable Objects & Additional Scripts

These changes don't alter the behavior of script deployment. Existing projects containing the Deploy-Once and Deploy-Change folder structures are not affected, and you don't have to rename them unless you want to. 

Migrating from the old to the new folder structure

Projects created before 1.12 will still use the old Deploy-Once / Deploy-Changes style folder structure. If you want to use the new folder names, you can migrate your existing projects. To do this:

  1. Open your .sqlproj file in a text editor.
  2. Find the <DeployOnceSubFolder> element and replace it with:

    <DeployChangesSubFolder>Programmable Objects</DeployChangesSubFolder>
  3. Save the .sqlproj file.
  4. In Visual Studio, open the project and rename the following ReadyRoll project folders:
    • rename Deploy-Once to Migrations
    • rename Deploy-Changes to Programmable Objects

Migrating from the new to the old folder structure

If you want to carry on using the old folder structure for ReadyRoll projects you create after installing 1.12:

  1. Open your .sqlproj file in a text editor.

  2. Find the <DeployOnceSubFolder> element and replace it with:

  3. Find the <DeployChangesSubFolder> element and replace it with:

  4. Save the .sqlproj file.
  5. In Visual Studio, open the project and rename the following ReadyRoll project folders:
    • rename Migrations to Deploy-Once
    • rename Programmable Objects to Deploy-Changes (if it exists)


Didn't find what you were looking for?