SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS package version control


SSIS package version control

Author
Message
yonision
yonision
SSC Journeyman
SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)

Group: General Forum Members
Points: 99 Visits: 164
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



Tom Van Harpen
Tom Van Harpen
SSC Eights!
SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)

Group: General Forum Members
Points: 908 Visits: 1102
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?
yonision
yonision
SSC Journeyman
SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)

Group: General Forum Members
Points: 99 Visits: 164
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?



Tom Van Harpen
Tom Van Harpen
SSC Eights!
SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)

Group: General Forum Members
Points: 908 Visits: 1102
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.
Tom Winter
Tom Winter
Grasshopper
Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)

Group: General Forum Members
Points: 24 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.
Hiawatha Tiller
Hiawatha Tiller
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 92
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.
Tom Van Harpen
Tom Van Harpen
SSC Eights!
SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)

Group: General Forum Members
Points: 908 Visits: 1102
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
Tom Van Harpen
Tom Van Harpen
SSC Eights!
SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)SSC Eights! (908 reputation)

Group: General Forum Members
Points: 908 Visits: 1102
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.
Stad
Stad
Valued Member
Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)

Group: General Forum Members
Points: 72 Visits: 121
Matt,

Do you ahve any idea how Subversion handles SSRS projects?

Thanks!
Stad.
Matt Horton
Matt Horton
Valued Member
Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)

Group: General Forum Members
Points: 56 Visits: 93
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.
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