Post reply

Versioning Control for SQL Server

  • November 9, 2011 at 8:35 am

    #390812

    Yesterday I posted a question which has gotten no responses as of yet so maybe I need to start a new thread with a totally different question relating to the same topic. I'm fairly new to this DBA world, what kind of versioning/source control do you guys use out there for SQL Server? What works/doesn't work? My group is considering TFS. Any input?

  • November 9, 2011 at 8:40 am

    #1405268

    We use subversion, which handles chek-in.outs, versioning , deployment etc... its a good product but does not tie into SQL server in a way that I would like.

    I would perfer to use TFS, but as we have mixed environemnts it is not possible.

  • November 9, 2011 at 9:00 am

    #1405287

    Our developer team uses Redgate Source Control

  • November 9, 2011 at 9:12 am

    #1405295

    Thanks Steveb. There seems tobe very little documentation for TFS out there. I think it'll be a process of trial and error all the way. 🙂

  • November 9, 2011 at 10:16 am

    #1405366

    http://www.red-gate.com/products/sql-development/sql-source-control/ + subversion as the actual source control system.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • November 9, 2011 at 1:01 pm

    #1405439

    Thank you all.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply