Versioning SQL Objects

• Mr. Cursor

  Old Hand

  Points: 385

  More actions

  March 8, 2013 at 3:12 am

  #275012

  Good morning set-based thinkers.

  I wonder if you can help me. In my previous contract, as part of a DBA team, I helped maintain about 1800 databases over 97 servers, with thousands of stored procs.

  We had a slick release management process based on Visual SourceSafe, and we used the VSS tokens within the sprocs to embed the version info etc. into the comment block upon each check in.

  My next contract finds me somewhere that has zero release management. As part of my work I have proposed a system similar to the one I have experience with, as I know that it works.

  However, it has hit a stumbling block with my customer, because he has done thirty seconds of Googling and discovered that VSS is only on extended support until 2017. He's concerned that I'm proposing something with built-in obsolescence.

  I think that he has a point. Kind of. Four years is an eternity for the IT here. It would be ample time to establish a viable source code control system - and then start looking for an alternative that we can migrate to.

  But - my question is - am I missing a trick?

  I only know VSS. I know that TFS can't embed version info as it doesn't have keyword expansion. Or am I wrong?

  Can Git or Subversion do this?

  Will Red Gate source code control do this?

  What's your solution?

  Mr. C