Database DevOps with Redgate Data Tools

Sign in to queue

The Discussion

  • User profile image

    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

    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

    @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

    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

    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