Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Source Control in SQL Server


Source Control in SQL Server

Author
Message
Vasant Raj
Vasant Raj
SSC Veteran
SSC Veteran (201 reputation)SSC Veteran (201 reputation)SSC Veteran (201 reputation)SSC Veteran (201 reputation)SSC Veteran (201 reputation)SSC Veteran (201 reputation)SSC Veteran (201 reputation)SSC Veteran (201 reputation)

Group: General Forum Members
Points: 201 Visits: 137
Comments posted here are about the content posted at temp
Noel Kennedy
Noel Kennedy
SSC-Enthusiastic
SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)

Group: General Forum Members
Points: 118 Visits: 57
I have found the following significant irritations when using Managmenent studio source control:

1. It creates 'connection objects' in the project, these can be very confusing and dangerous as they can easily point to your live environment. This means when you open a script in source control you have to carefully check which environment, management studio has decided to open a connection to.

2. It doesn't sort scripts in alphabetical order?? The fact this feature is missing is extremely aggrevating and is surely very easy to develop.

3. Getting source safe to create the desired folder structure, is impossible (and if not impossible very difficult). Not sure if this is management studio's fault as VSS is
David Atkinson
David Atkinson
SSC Rookie
SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)

Group: General Forum Members
Points: 39 Visits: 507

I've always shied away from using any of the source control integration offered by editors/IDEs, instead using the source control client itself for check-outs and check-ins. I can't quite put my finger on why I do it this way, because I definitely like the idea of integration. I think it's because I know that regardless of the application/editor I eventually use to edit my source controlled files, using the same UI for the check-out/in operation is somehow comforting to me - I know that it's something that I've done successfully before, it doesn't involve any more configuring of source control settings, and I have confidence that it will work.

I'd be curious to know if it's just me, or whether most people actually prefer using the built-in source control integration that various IDEs like SSMS and Visual Studio provide.

David Atkinson, Red Gate Software


Noel Kennedy
Noel Kennedy
SSC-Enthusiastic
SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)

Group: General Forum Members
Points: 118 Visits: 57
pretty bad as well.

4. Everytime i open a solution, I get a message about solution vs project binding. While this is less important, it reminds me everytime i use 'source control' that this is a shoddy implementation.
Noel Kennedy
Noel Kennedy
SSC-Enthusiastic
SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)SSC-Enthusiastic (118 reputation)

Group: General Forum Members
Points: 118 Visits: 57
Hi david,

I used to use VSS's client directly as you described. I have found that management studio saves a marginal amount of time as i don't have to go in and out of QA & VSS all the time as was the case with sql 2000. SQL 2005 doesn't replace the VSS client completely as I still have to use this to sort out any messes made by management studio & do things like labelling.
David Atkinson
David Atkinson
SSC Rookie
SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)

Group: General Forum Members
Points: 39 Visits: 507

Hi Noel,

For me it's a trade off between a "marginal" improvement and the familiarity of the source control client. If I'm going to have to have my source control client open anyhow (which I do), it's quite a trival operation to alt-tab to it and perform whichever operation I need. As you point out, there are some functions that are only available in the client, so I guess you probably have yours open too. If labelling (and the other functions that you can't do in SSMS) were integrated, would that make your life a lot easier? I definitely agree with the principal that the fewer tools that are required to do a job, the better.

David


Rob Sanguin
Rob Sanguin
SSC-Enthusiastic
SSC-Enthusiastic (114 reputation)SSC-Enthusiastic (114 reputation)SSC-Enthusiastic (114 reputation)SSC-Enthusiastic (114 reputation)SSC-Enthusiastic (114 reputation)SSC-Enthusiastic (114 reputation)SSC-Enthusiastic (114 reputation)SSC-Enthusiastic (114 reputation)

Group: General Forum Members
Points: 114 Visits: 78

I agree with Noel wholeheartedly, the lack of alphabetical sorting is extremely annoying and wastes precious time.

However I much prefer to have source control integrated into the 1 piece of s/w where I do all of my DB development (SSMS), so that's a big plus for me.

My other bug-bear at the moment is that when initially adding a file to a project it is created as binary so I can't compare different versions, I have to go into source safe -> right click the file -> properties and change binary to text. This would be a useful feature for SSMS too.

Overall though, it's a good start, but could try harder!


David Atkinson
David Atkinson
SSC Rookie
SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)

Group: General Forum Members
Points: 39 Visits: 507

Are there any other source control features that would make sense to control from within SSMS?

Noel mentioned labelling. Would this be something that you would want to do from inside SSMS? Or are some features best left to the source control client?

David


SQLZ
SQLZ
SSC Eights!
SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)

Group: General Forum Members
Points: 874 Visits: 940

Amongst the other problems that have been mentioned, for me, the biggest problem with VSS integration was something the author alluded to in the conclusion:

"...whenever a script has been updated, the only way to reflect the changes in the source control is to script the file and update the changes". 

And vice-versa - when you change your source control file, check it in you then have to remember to apply those changes to the database.

Which is why I developed an integrated source control app that automatically applies the changes to the SQL Server when a script is checked in (link in sig.  small plug ).  Oh, and the source control database sits on a SQL Server.

But then, as David indicated, some people shy away from the integrated editors - which I can also relate to.

So I then thought I'd throw in intelliense - only for Red-Gate to come and steal my thunder.



Karl
source control for SQL Server
sqltung
sqltung
SSC Veteran
SSC Veteran (216 reputation)SSC Veteran (216 reputation)SSC Veteran (216 reputation)SSC Veteran (216 reputation)SSC Veteran (216 reputation)SSC Veteran (216 reputation)SSC Veteran (216 reputation)SSC Veteran (216 reputation)

Group: General Forum Members
Points: 216 Visits: 585
Visual Studio Team Edition for Database Professionals includes improved source control functionality. In addition, you can associate assigned work tasks with source changes.

I attended a product launch last week during which it was indicated that the Team Edition suite of products is where Microsoft is investing their source control development budget; Visual Source Safe is not being developed anymore.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search