I need a solution for SQL Server Database object version control. I need recommendations that work with studio manage

We are having trouble managing the database objects like store procedures.

I need suggestions for hosted version control

Thanks,
Rich
Rich-AlaskaAsked:
Who is Participating?
 
Rich-AlaskaAuthor Commented:
Have you used the red-gate or know anyone. I've seen this one and Apex
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 
Vadim RappCommented:
I did not use version-control product, but I do use another product from red-gate - "sql compare", and in the past I used SQLEdit from Apex. Red-gate product has always been solid, and I'm still using it, while Apex has been a disaster that had more bugs than useful functionality. So, to the degree that past experience is an indication of future results, if I needed this product, I would certainly try red-gate first.
0
 
David ToddSenior DBACommented:
Hi,

If all build scripts are in a version control, and there is the discipline to add the appropriate comment into the script that has a version number and change comment, then it becomes fairly easy.

HTH
  David
0
 
PortletPaulCommented:
>>"and there is the discipline"
no tool by itself solves the problem; configuration management requires discipline.
0
 
Rich-AlaskaAuthor Commented:
Really ?

I'm looking for someone with previous hands-on experience with a product for actual feedback
0
 
Ryan McCauleyData and Analytics ManagerCommented:
I know there's already an accepted answer and you're looking for something that integrates with Visual Studio, but here's some detail on the custom solution we deployed to track code changes:

http://www.experts-exchange.com/Database/MS-SQL-Server/SQL-Server-2005/A_6237-Lightweight-SQL-source-control-using-a-single-stored-procedure.html

While it doesn't allow you to track object changes to a version deployment specifically, it does track all changes (including those made on the fly in SSMS, not through a deployment), and it's a good failsafe to have in place. If you're having issues with a stored procedure returning expected results, it's just a query away to see if it's changed recently or compare it to the previous version, even if it was edited outside your code development tool.
0
 
Anthony PerkinsCommented:
Ryan,

Thank you for sharing that.  It looks very promising and I will definitely look at it more in depth.  

Some questions though:
1. Have you considered updating the code to use OBJECT_DEFINITION instead of the deprecated syscomments?
2. What about broadening it to VIEWs and Functions?

Again thank you.
0
 
Ryan McCauleyData and Analytics ManagerCommented:
@ACPerkins: It currently handles everything with a line in syscomments, which includes stored procedures, functions, views, and defaults. I've considered extended it to cover tables as well, but haven't ever sat down to hammer out the code.

As for OBJECT_DEFINITION, I've also considered the switch but just never executed it - it was actually written originally for SQL 2000 and had a cursor in it (since NVARCHAR(MAX) wasn't an option), which has since been replaced. I'll actually take a look at making both of those changes - it's probably due for an update :)
0
 
Anthony PerkinsCommented:
It currently handles everything with a line in syscomments, which includes stored procedures, functions, views, and defaults.
That is good to know, for some reason I thought it just handled Stored Procedures.
0
 
PortletPaulCommented:
@Anthony & Ryan

this dialog would be more useful on the article wouldn't it? It does look like something many folks could benefit from.
0
 
Anthony PerkinsCommented:
Fair enough.  Please delete all off-topic comments.
0
All Courses

From novice to tech pro — start learning today.