June 8, 2009 at 12:19 pm
All those files except the suo and user files
June 8, 2009 at 2:46 pm
Thank you Matt.
June 9, 2009 at 8:46 am
Hi, We're also using SVN and wan't to know if there is any possibility that the merge function would work for a dtsx file modified by 2 developers. I can't imagine there would be any way that a source control could integrate 2 sets of mods to a dtsx with the pipeline relying so heavily on the stored meta-data and lineage ID's, it would have to map lineage ID's on a merge and that would be crazy.
thoughts?
June 9, 2009 at 8:54 am
I haven't played a ton with dtsx files. I do know that rdl files it's a huge pain. Since files are appended from the top, merging is a nightmare. Assuming dtsx files appending at the bottom, it should be easier. As a rule, we currently don't allow two developers to work on the same dtsx file.
July 14, 2009 at 8:57 am
Matt Horton (5/1/2008)
You can search for previous versions through SVN, but SQL server doesn't store previous versions as far as I am aware.
We also use SVN and use its keyword substitution features to populate the VersionComment property of each package to add version control information. That way it is possible to see what revision of a package has been deployed to each environment.
And I wouldn't try merging dtsx files using any source code system. We treat them like binary files and use SVN locks to prevent two developers from working on the same package at once.
October 20, 2009 at 10:54 am
And I wouldn't try merging dtsx files using any source code system. We treat them like binary files and use SVN locks to prevent two developers from working on the same package at once.
We also do this, and it works great.
October 20, 2009 at 11:53 am
daphneds (10/20/2009)
And I wouldn't try merging dtsx files using any source code system. We treat them like binary files and use SVN locks to prevent two developers from working on the same package at once.
We also do this, and it works great.
Agreed, I've done it with VSS and TFS primarily and I never try to do a merge.. All in, all out..
CEWII
October 20, 2009 at 4:28 pm
daphneds (10/20/2009)
And I wouldn't try merging dtsx files using any source code system. We treat them like binary files and use SVN locks to prevent two developers from working on the same package at once.
We also do this, and it works great.
Hmmm? Can I assume that by "We also do this", that you mean that you also use SVN prevent more than one developer from editing the same DTSX at the same time? As opposed to "We also" merge DTSX files (which seems like an impossible nightmare)?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
October 28, 2009 at 1:01 am
VSS
November 6, 2009 at 9:23 am
Where is the version comment property? How do you access this from a package deployed as a sql deployment?
thanks, tom
December 8, 2009 at 1:14 pm
The following tool, while built for versioning entire SQL Sever (and works with SourceSafe, Subversion and TFS) - also does SSIS packages:
December 8, 2009 at 1:23 pm
yonision (12/8/2009)
http://www.nobhillsoft.com/Randolph.aspx%5B/quote%5D
What does this do for SSIS that subversion doesn't?
December 8, 2009 at 2:26 pm
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?
December 9, 2009 at 5:46 am
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.
December 10, 2009 at 6:46 am
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.
Viewing 15 posts - 31 through 45 (of 56 total)
You must be logged in to reply to this topic. Login to reply