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


SSIS package version control


SSIS package version control

Author
Message
vikas.palaskar
vikas.palaskar
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 20
We also use the SVN, but its very defficult to make out the what exactly is changed. Do you know how to understand it.
Matt Horton
Matt Horton
Grasshopper
Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)

Group: General Forum Members
Points: 20 Visits: 93
Because of how rdl builds I've found adding notes when you commit helps a ton.
rock on dude
rock on dude
SSC Veteran
SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)

Group: General Forum Members
Points: 222 Visits: 10576
The .dtsx files are absolutely abysmal for source control. Impossible to merge or get any idea of what was changed from version to version, so the only thing you can rely on are commit comments. MS could make this so much better by separating the code used to drive developer studio from the steps to minimize the changes to the files. Perhaps split the files into two or put all the horrible gobbledygook somewhere at the bottom? Right now they might as well be completely binary.
Marios Philippopoulos
Marios Philippopoulos
SSCommitted
SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)

Group: General Forum Members
Points: 1954 Visits: 3740
Vivien Xing (5/7/2008)
I sent a feedback to Microsoft. Package version feature will be considered for the next major release. If you have any comments to add on, here is the link:

SSIS Package Version Change Tracking Log in SSMS - SQL2005 & SQL2008
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=341995


Thank you for suggesting this to Microsoft.

Adding the ability of tracking last modified date in packages through querying msdb.dbo.sysssispackages will also help in maintaining a Disaster/Recovery environment with the latest changes in production.

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables
Persisting SQL Server Index-Usage Statistics with MERGE
Turbocharge Your Database Maintenance With Service Broker: Part 2
Vivien Xing
Vivien Xing
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1292 Visits: 2204
Marios Philippopoulos (1/27/2011)
Vivien Xing (5/7/2008)
I sent a feedback to Microsoft. Package version feature will be considered for the next major release. If you have any comments to add on, here is the link:

SSIS Package Version Change Tracking Log in SSMS - SQL2005 & SQL2008
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=341995


Thank you for suggesting this to Microsoft.

Adding the ability of tracking last modified date in packages through querying msdb.dbo.sysssispackages will also help in maintaining a Disaster/Recovery environment with the latest changes in production.

Good point thinking about DR. I am glad that Microsoft heard our voice. It took a couple of years to see the change.

Anyone has tried SQL Server Denali CTP yet? Hope the version tracking feature meets our expectations.
Marios Philippopoulos
Marios Philippopoulos
SSCommitted
SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)

Group: General Forum Members
Points: 1954 Visits: 3740
Vivien Xing (1/28/2011)
Marios Philippopoulos (1/27/2011)
Vivien Xing (5/7/2008)
I sent a feedback to Microsoft. Package version feature will be considered for the next major release. If you have any comments to add on, here is the link:

SSIS Package Version Change Tracking Log in SSMS - SQL2005 & SQL2008
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=341995


Thank you for suggesting this to Microsoft.

Adding the ability of tracking last modified date in packages through querying msdb.dbo.sysssispackages will also help in maintaining a Disaster/Recovery environment with the latest changes in production.

Good point thinking about DR. I am glad that Microsoft heard our voice. It took a couple of years to see the change.

Anyone has tried SQL Server Denali CTP yet? Hope the version tracking feature meets our expectations.


Unfortunately, for the time being I'm stuck with SQL 2008, so I have to make do with the verbuild column of msdb.dbo.sysssispackages.

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables
Persisting SQL Server Index-Usage Statistics with MERGE
Turbocharge Your Database Maintenance With Service Broker: Part 2
jiamin_zeng
jiamin_zeng
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 5
Thank you, Vivian, for submitting a feedback to Microsoft. I have just added my vote to your post. Per the comment from Microsoft, this would be fixed in Denali. My question is, in the meantime, how does one know a package deployment is successful? For me, I have to do it the hard way - I have to first delete all the existing packages and then redeploy all of them to ensure the server has the latest. Does anyone have a better suggestion? Thanks.
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