Version details in SSIS Project Properties in SSDT are not usable - by Julie Koesmarno

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


13
0
Sign in
to vote
ID 863762 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 4/29/2014 4:47:11 PM
Access Restriction Public

Description

In SSDT (Visual Studio 2012/2010), you can change Version details (VersionBuild, VersionMajor, VersionMinor and VersionComments) in the Project Property Pages via Project > Properties menu. 


It seems that:

1. These VersionBuild, VersionMajor, VersionMinor and VersionComments values are not carried through to the deployed project in Integration Services Catalogs in SQL Server 2012.

2. The user interface in SSDT changes some of the Version values in dtproj file for the first time, but never updates them with subsequent changes. 


A few more observations relating to dtproj and ispac files:

a. When VersionBuild, VersionMajor, VersionMinor and VersionComments are changed manually in dtproj file, the project does not show the information on the UI at all when it is reopened.

b. The ispac file (inside @Project.manifest) does not copy across the VersionBuild, VersionMajor, VersionMinor and VersionComments values from dtproj 



My questions are:

i. Is there a purpose of having these VersionBuild, VersionMajor, VersionMinor and VersionComments fields in the SSIS Project Property pages? Or is there a plan for an upcoming release to make them more "usable"?

ii. There are version_build, version_major, version_minor and version_comments columns in [SSISDB].[internal].[packages]. Where are these values meant to be populated from? Are these meant to be at the "project" level, given that Visual Studio / SSDT allows the user interface access at the project level (albeit not working properly).

iii. If it had been working properly, would you use it? I can see it being very useful from auditing point of view (and for ease of choosing which version to conveniently revert back to, at a pinch).


For further information, please visit http://www.mssqlgirl.com/sql-server-2012-ssis-project-versions.html
Sign in to post a comment.
Posted by Microsoft on 6/1/2016 at 8:48 PM
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SSIS. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product
2.     Scenarios reported in the bug are not common enough


If the issue is a critical business interruption, please call CSS (Customer Support Services).

Thanks again for reporting the product issue and continued support in improving our product.
Posted by LuboD on 2/15/2016 at 3:18 AM
I am using SQL Server 2014 and experiencing no improvement in this area.
It would be really useful if I could confirm deployed version back to my Git source Control.