How can I tell the version of each lifecycle database using SSC?

• 
  SQL Source Control does not do this out of the box. Neither do other state based source control tools. SQL Change Automation (and other migration based tools) give you this as a side-effect of the deployment process, not solely for auditing purposes.
  
  Most people manage what version is deployed where in a separate tool. Something like Jenkins, Octopus Deploy or Azure DevOps Services. This is consistent with, for example, the way most people manage their application releases. It's unusual to update the application in some way just so you can see what's deployed.
  
  If you were desperate to achieve this in the database, you could add a post deploy script to your deployment process to (for example) squirt the upgrade script, a timestamp and the Octopus release number into an auditing table. This would provide similar functionality to what you get with an SCA project.
  
  Or you could use DLM Dashboard. 😉

  AlexYates April 29, 2019 15:42

  - 0 +
• 
  Thanks, @AlexYates.  I figured as much - just wanted to make sure I wasn't missing anything.  I do like having a version stamp in individual DBs as it helps to identify version as they get backed up and restored elsewhere. Could even be an extended property.  It's also helpful while we don't have CI servers in place.  Post-deploy script option seems reasonable.  
  
  Thank you,
  
  -Peter

  PeterDaniels April 29, 2019 16:59

  - 0 +
• 
  Makes sense.
  
  But you should get a CI server in place. ;-P

  AlexYates April 29, 2019 17:02

  - 0 +
• 
  Couldn't agree more, Mr Yates.
  Our org moves...
  s
  l
  o
  w
  l
  y
  
  

  PeterDaniels April 29, 2019 18:13

  - 0 +

Add comment

Please sign in to leave a comment.