THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Andy Leonard

Andy Leonard is CSO of Linchpin People and SQLPeople, an SSIS Trainer, Consultant, and developer; a Business Intelligence Markup Language (Biml) developer; SQL Server database and data warehouse developer, community mentor, engineer, and farmer. He is a co-author of SQL Server 2012 Integration Services Design Patterns. His background includes web application architecture and development, VB, and ASP. Andy loves the SQL Server Community!
Note: Comments are moderated. Spam shall not pass! </GandalfVoice>

Survey: T-SQL Source Control?

One or two quick survey questions:

  1. Do you manage T-SQL scripts in source control?
  2. If so, which source control product / platform do you use?

:{> Andy

Note: I moderate comments, so your comment will take some time to publish.

Published Tuesday, March 09, 2010 8:00 AM by andyleonard

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

SJC said:

Yes, when I remember/am urged to, we use Subversion with the Tortoise front end.

March 9, 2010 7:29 AM
 

jamiet said:

1. Yes, always!

2. Depends what project I'm on. If I get the choice then its TFS & Datadude. At the place I am at the moment they use SVN for source control and author the scripts in SSMS.

March 9, 2010 7:43 AM
 

Erik said:

Yes, absolutely.  Subversion.  Is there any other option?

March 9, 2010 7:47 AM
 

Sean said:

Yes

Subversion

March 9, 2010 7:52 AM
 

DomreiRoam said:

We do use Subversion for versionning. We hae some T-SQL script into this but it is not systematic. We use it mainly for SSIS.

March 9, 2010 8:10 AM
 

Stefan said:

Yes

Visual Source Safe (not my choice, and NO I don't like it)... integration into BIDS is nice but other than that... junk.

March 9, 2010 8:25 AM
 

Todd Nelson said:

Yes.  Source Gear Vault.

March 9, 2010 8:33 AM
 

Thierry said:

Yep, 2 times a day, automated at 12:30 and 23:30

To a sourcesafe repository.

The triggers, views, functions and tables too.

We can rebuild a complete database (except for it's data) from those snapshots.

March 9, 2010 8:36 AM
 

Alexander Kuznetsov said:

Yes. Subversion is the king, much better that the alternatives.

March 9, 2010 8:40 AM
 

Eric Wisdahl said:

I use source control for some of the T-SQL that I write.  If it is ddl we always keep it in source control.  If it is a personal query, I sometimes use it... depends on the project.

I currently use perforce.  Until recently we used source safe (couldn't get licenses for perforce and the two were the only approved source control tools).  

March 9, 2010 9:04 AM
 

mjswart said:

one more for yes, subversion.

March 9, 2010 9:45 AM
 

Paul Nielsen said:

yes, whatever the client uses for source control. recent jobs include SourceSafe and TFS.

March 9, 2010 9:46 AM
 

Jake Morrison said:

Yes, we currently store them in sourcesafe, I'm pushing to move to SVN.

March 9, 2010 9:54 AM
 

LeoPasta said:

Yes, we use Git in our shop

March 9, 2010 10:03 AM
 

Ron said:

Yes, we use SVN.

March 9, 2010 10:28 AM
 

Kevin said:

Yes, I use TFS and the VSTS database projects.  Autogenerating deployment scripts is worth it alone.

March 9, 2010 10:34 AM
 

WIDBA said:

We use Visual Studio with Database Projects and our source control is from Seapine - it integrates alright - not as well as others I am sure.

March 9, 2010 10:52 AM
 

Adam Machanic said:

1. Always. If the customer doesn't have their stuff in source control, I put it there for them.

2. Whatever the customer is using. TFS, VSS, SVN (my favorite), and unfortunately CVS a couple of years ago.

March 9, 2010 10:54 AM
 

Dylan Finney said:

Another happy TFS user here.

March 9, 2010 11:01 AM
 

Tim of Angle said:

Subversion and TortoiseSVN.

March 9, 2010 11:07 AM
 

Sankar Reddy said:

+1 for svn

March 9, 2010 12:36 PM
 

James Luetkehoelter said:

+1 for svn as well, but have to work with what the customer is using..

March 9, 2010 1:34 PM
 

Code *itch said:

Absolutely. SQL is code.  Code gets version controlled.  QED.

Anyone who doesn't organize their SQL into human-readable script files, just like their compiled code, should be taken out to the whuppin' shed.

Which version control system?  By force, VSS.  Effective and over the last 15 years I've learned to cope with its faults and bugs.  If I had a choice, it wouldn't be VSS.

March 9, 2010 3:05 PM
 

AaronBertrand said:

Looks like my previous reply was moderated away?  We recently switched from VSS to SVN.  I won't say anything negative about this experience because maybe that's why I was censored.  :-)

March 9, 2010 3:15 PM
 

andyleonard said:

Hi Aaron,

  Nope, just not published in a timely fashion.

:{> Andy

March 9, 2010 3:19 PM
 

Ramdas said:

We use TFS for source control.

March 9, 2010 3:31 PM
 

Boyan Penev said:

I have used subversion in the past, and presently I am using TFS - both come with some drawbacks - most importantly the lack of integration between them and SQL Server.

I have also created the folowing Connect suggestion - Native Source Control (Microsoft commented that they are thinking about it from the "tools perspective"). I would be really keen to get more suggestions about best approach to implementing a similar feature in SQL Server:

https://connect.microsoft.com/SQLServer/feedback/details/518835/native-source-control

March 9, 2010 3:57 PM
 

Aaron Lowe said:

TFS via VSDBPro - love it!

March 9, 2010 4:16 PM
 

Phil said:

1. Yes, no, sometimes, depends ... arrrgh

2. Currently bunch of T-SQL scripts with AnkhSVN in Visual Studio Pro. Also looking into the new SQL Source Control from Red-Gate (loving the SSMS integration).

March 9, 2010 5:48 PM
 

AmosFiveSix said:

Subversion/VisualSVN Server/TortoiseSVN

I use it for my views, functions and SSIS packages. Eventually I'll be putting in some of our more frequently used queries that aren't in there as actual views, plus some template/snippets. I'm not involved in creating any of the actual tables, so none of that's in there.

I wouldn't want to develop without some sort of version control for my SQL.

March 10, 2010 8:53 AM
 

Barry said:

Yes.  I'm actually amazed that so many places DON'T have the SQL code in Source Control.

Why is that?  Is it because SQL is considered by some to be the red-headed stepchild of real-coding ?

I use VSS.

March 10, 2010 9:40 AM
 

AaronBertrand said:

Barry, I think part of the reason is that a lot of people make changes by using the visual designers.  If they don't notice the Script button is there, they have little else to do but record a video of them pointing and clicking through the dialogs.  :-)

On a more serious note, I think some people use backups as their source control.  After all, it can be complicated work to get a label to represent an autonomous point-in-time for a database, where all objects are in a consistent state.  (I'm not saying it's not do-able or worthwhile, just that it's too much work for some people.)  Whereas with a backup, you know that the contents (including data) were consistent at that point in time.

March 10, 2010 11:12 AM
 

mwalbert said:

subversion, tortoise front-end

March 10, 2010 4:09 PM
 

merrillaldrich said:

Yes, but badly. Using TFS.

March 11, 2010 9:04 AM
 

Eric said:

1)  Most definitely!

2)  Does setting a script read-only on a shared drive count?  My current place is a little more sophisticated and using TFS nowadays.  

March 11, 2010 10:43 AM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

My Company


Other Blog

Check out my personal blog...
http://andyleonard.me

Contact Me

Twitter: @AndyLeonard
Email: andy.leonard@gmail.com

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement