Database DevOps with Redgate Data Tools

Download this episode

Download Video

Download captions

Download Captions

Description

DevOps is a wonderful thing. With it comes better collaboration across teams for early feedback in the development cycle, joint accountability for fixing problems, and working together to get value to customers quickly and efficiently. When considering the database, it can be tricky to extend DevOps processes used for the application to the database. In this demo-heavy session, you'll see how Redgate Data Tools allow you to extend DevOps processes to your SQL Server or Azure SQL databases and reap the benefits of increased productivity, agility, and performance across your teams.

Find out more details by visiting Redgate Data Tools page.

For more information, check out these courses on Microsoft Virtual Academy:

Day:

0

Session Type:

Pre-recorded

Code:

T101

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image
      aljj

      the add column script shouldn't check first if the column already exist? As is, it is not repeatable (run it twice and 2nd time will error). In my experience, SQL DevOps exists since early 2000 and it always used repeatable scripts created by developer during development

    • User profile image
      bkstill

      How are script failures dealt with during deployment? If there are multiple migration scripts are they transactional? If one fails do they all fail?

    • User profile image
      cashfoley

      @aljj: It's not necessary to add the 'error prone' conditional code.  The tool assures it won't run twice.  That's key to how this works.

    • User profile image
      Ben

      My big question is: how can I roll back my changes, if I make a mistake and need to go back to a previous release?

    • User profile image
      David Atkinson

      @Ben - If you've deployed, the best practice is to roll forward with a migration script to fix the issue. If you haven't deployed and you wish you revert your dev environment, simply delete the errant migrations scripts from the project, which has the effect of returning the object changes to the DBSync window, select the ones you wish to roll back, right click and select Revert Selected Objects from the context menu. This action applies the undo script to your dev environment.

    • User profile image
      DBATrollman

      I would be interested in another video where you show your first script in creating the database schema or migrating a database into VS2015 to start the process.

    Add Your 2 Cents