Using migration scripts from command line on unlinked DB

Comments

• David Pond Redgate › Posts: 25 Bronze 1

  March 6, 2012 1:27PM

  Hi Robert, I've sent you an e-mail with a possible solution.
  
  We will be supporting this feature in SQL Compare 10.1 which will be released in the next couple of weeks.
  
  David

  0 · Share on Twitter
• dmcaldwell Posts: 2

  March 2, 2013 12:07PM

  Would you mind posting the possible solution on the forum so its available for all of us?

  0 · Share on Twitter
• David Pond Redgate › Posts: 25 Bronze 1

  March 4, 2013 9:00AM

  I sent RobVK an early build of SQL Compare with a description of some new commandline switches. These switches are now in the current release of SQL Compare (see below). We're working on an easy to use solution, but you can get started with these commands.
  
  This is the landing page for information on CI for databases. http://www.red-gate.com/products/sql-de ... tegration/
  
  RobVK needed to checkout his migrations folder and use the /migrationfolder switch. The /scriptsfolderxml switch is also required because SQL Compare will need to make additional checkouts from the version control system.
  
  /abortonwarnings: none | medium | high
  Sets the warning level at which SQL Compare command line will abort.
  
  /assertidentical
  Returns exit code zero in the event both database schemas are identical. This can be used at the end of the CI process to confirm that the local copy of the production DB has been successfully updated.
  
  /migrationfolder
  This is a path to a directory containing the migration scripts to be used.
  
  /migrationfolderxml [deprecated]
  /migrationfolder should be used instead of this option. By allowing the CI system to check out the migrations folder it can display information about recent commits.
  
  /revision1, /revision2
  When used with /scripts, it allows SQL Compare to identify the correct migrations scripts. This is necessary because a script folder does not contain information on which revision it is.
  When used with /sourcecontrol it also specifies which revision will be checked out by SQL Compare.
  
  /scriptfolderxml
  This is a path to a text file that contains an xml fragment which describes a connection to a VCS. This fragment can be copied from the extended properties of a live database connected to SQL Source Control.
  
  /versionusername1, /versionpassword1
  These are you username and password to connect to the VCS system. This is required when using /sourcecontrol or when migration scripts are being used.
  
  Sample from a Nant script:

  <target name="generate_upgrade_script_schema">
        <exec program="${sqlcompare.executable}" resultproperty="returncode" failonerror="false">
              <arg value="/scripts1:"${latest.scriptsfolder}""/>
              <arg value="/revision1:${latest.revision}"/>
              <arg value="/sourcecontrol2"/>
              <arg value="/revision2:${production.revision}"/>
              <arg value="/scriptsfolderxml:${repo.location.xml}"/>
              <arg value="/migrationfolder:${migration.folder}"/>
              <arg value="/AbortOnWarnings:high"/>
        </exec>
  </target>
  

  0 · Share on Twitter