SSIS package version control

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 Integration Services » SSIS package version control

57 posts, Page 5 of 6

«««2 3 4 5 6 »»

SSIS package version control

Rate Topic

Display Mode

Topic Options

Author

Message

yonision

Posted Tuesday, December 08, 2009 1:14 PM

Valued Member

Group: General Forum Members
Last Login: Wednesday, April 03, 2013 11:39 AM
Points: 52, Visits: 151

The following tool, while built for versioning entire SQL Sever (and works with SourceSafe, Subversion and TFS) - also does SSIS packages:

http://www.nobhillsoft.com/Randolph.aspx

Post #830963

Tom Van Harpen

Posted Tuesday, December 08, 2009 1:23 PM

Old Hand

Group: General Forum Members
Last Login: 2 days ago @ 8:15 AM
Points: 386, Visits: 901

yonision (12/8/2009)

The following tool, while built for versioning entire SQL Sever (and works with SourceSafe, Subversion and TFS) - also does SSIS packages:
http://www.nobhillsoft.com/Randolph.aspx

What does this do for SSIS that subversion doesn't?

Post #830976

yonision

Posted Tuesday, December 08, 2009 2:26 PM

Valued Member

Group: General Forum Members
Last Login: Wednesday, April 03, 2013 11:39 AM
Points: 52, Visits: 151

It simply relieves you of the responsibility of maintaining it. you work on your SSIS packages, whenever you change anything, the history is added into subversion. you dont need to do anything, youre free to focus on your work, knowing that the history is always there in your repository. see?

Post #831020

Tom Van Harpen

Posted Wednesday, December 09, 2009 5:46 AM

Old Hand

Group: General Forum Members
Last Login: 2 days ago @ 8:15 AM
Points: 386, Visits: 901

No I don't see. When does it commit? on every save? If so that's a problem since we can only commit a buildable working version.
Red Gate is coming out with a similar product for Management Studio that integrates with Subversion. This will allow us to version all our stored procedures, views, triggers, udf's ect...
We are part of the beta group, can't wait.

Post #831307

Tom Winter

Posted Thursday, December 10, 2009 6:46 AM

Forum Newbie

Group: General Forum Members
Last Login: Friday, August 03, 2012 5:34 PM
Points: 8, Visits: 85

We're starting to use TortoiseSVN and it seems to work well. Previously we just made backup copies in the filesystem. We don't so anything fancy - no solutions or projects, just individual DTSX files.

Post #832162

Hiawatha Tiller

Posted Thursday, December 10, 2009 7:10 AM

Forum Newbie

Group: General Forum Members
Last Login: Yesterday @ 12:37 PM
Points: 2, Visits: 88

So I implemented the "svn:needs-lock" property to ensure that only one .dtsx package could be owned by a developer but now I'm getting annoying "check-out" prompts when viewing Data Flows. How are you other SVN users working around this? In this scenario I'm not wanting to grab a lock on the file, I just want to view it.

EDIT:
Let me throw some more information at you. I was experimenting a little and it seems the number of "check-out" prompts is directly related to the number of Lookup tasks in the Data Flow.

Post #832188

Tom Van Harpen

Posted Thursday, January 14, 2010 11:41 AM

Old Hand

Group: General Forum Members
Last Login: 2 days ago @ 8:15 AM
Points: 386, Visits: 901

Matt you mentioned using the keyword sub and update the revision comments.
From what I read SVN simply searches the document looking for a text string such as $Rev$ and then replaces it with a value such as $Rev: 12 $: This indicates that the revision of the package when committed was 12.
Do you simply put the value "$Rev$" into the version comments field. Then on commit will it update the working copy with the committed revision number?
thanks

Post #847795

Tom Van Harpen

Posted Thursday, January 14, 2010 5:05 PM

Old Hand

Group: General Forum Members
Last Login: 2 days ago @ 8:15 AM
Points: 386, Visits: 901

After some more looking i have the SVN keyword substitution working. Quite simple in fact. On the working directory right click on the folder that contains all the DTSX files - mouse over Tortoise SVN - click properties. Click New then select svn:keywords from the dropdown and for the value entered "Rev" and mark the checkbox to apply recursive this then set the property for every file in the folder. At this point I did a commit since each file was modified.
I didn't worry about other files (non-dtsx) since the property will be there but it will not perform the substitution unless the specific string is found within the file contents.
Next opened the solution and set the value of the Version Comments property on each package to $Rev$
Saved all then committed. Checked the version comments and found the version number in the comments field. Very slick, now I can setup my logging to include the SVN version number.

Post #848033

Stad

Posted Thursday, January 13, 2011 1:28 PM

SSC Rookie

Group: General Forum Members
Last Login: Monday, August 06, 2012 9:31 AM
Points: 28, Visits: 121

Matt,

Do you ahve any idea how Subversion handles SSRS projects?

Thanks!
Stad.

Post #1047549

Matt Horton

Posted Thursday, January 13, 2011 1:33 PM

Grasshopper

Group: General Forum Members
Last Login: 2 days ago @ 3:42 PM
Points: 18, Visits: 84

I use it with SSRS every day.

I would exclude the following types of files though (not check them in)

.data
.suo
.user

Since these are user specific they can cause problems if you have multiple people working on a solution.

Post #1047553

« Prev Topic | Next Topic »

57 posts, Page 5 of 6

«««2 3 4 5 6 »»

Permissions