June 2, 2012 at 3:03 pm
Comments posted to this topic are about the item SSIS 2012 - Versioning
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 2, 2012 at 5:59 pm
June 4, 2012 at 12:48 am
On your link provided it is stating something different.
http://msdn.microsoft.com/en-us/library/hh479588.aspx
The objects that are stored in the SSISDB catalog include projects, packages, parameters, environments, and operational history.
June 4, 2012 at 12:50 am
Imran Ashraf-452633 (6/4/2012)
On your link provided it is stating something different.http://msdn.microsoft.com/en-us/library/hh479588.aspx
The objects that are stored in the SSISDB catalog include projects, packages, parameters, environments, and operational history.
There's a difference between storing something and versioning something.
There's a lot of items stored on my hard drive, but none of them are versioned.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 4, 2012 at 6:51 am
Pretty straight forward question.
June 4, 2012 at 7:11 am
Interesting... so you have to roll back an entire project even if you only need a previous version of a single package?
June 4, 2012 at 7:13 am
sestell1 (6/4/2012)
Interesting... so you have to roll back an entire project even if you only need a previous version of a single package?
For the moment this seems to be the case, yes.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 4, 2012 at 9:05 am
bitbucket-25253 (6/2/2012)
Ah spoon feeding us on the basics ... I like that approach.
Spoon fed with cinnamon :satisfied:
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 4, 2012 at 9:38 am
Nice question - thanks, Koen!
June 4, 2012 at 9:40 am
The catalog.packages view holds version_minor, version_major, and version_build for each package, which seems to make packages pretty well versioned. It also holds version_comments with comments for a specific version of the package, and version_guid which is a globally unique identifier for the specific version of the package. In addition it holds package_format_version to tell us whether this is a version used for SQL2005, SQL2008, or SQL 2012. So I don't believe the idea that packages are not versioned in SSISDB holds water.
Environments are apparently not versioned.
Projects are versioned, albeit in a pretty limited manner; the catalog.projects view holds version_lsn and project_format_version, no major/minor version (also no build version, but that's probably irrelevant for a project).
The SSISDB database clearly has versioning for two of the three objects mentioned.
None of the offered answers appears to be correct.
If the question had been "which object types are versioned in the SSISDB catalog view catalog.object_version" the "correct" answer would actually have been correct, but the question was something very different and the correct answer was wrong.
Tom
June 4, 2012 at 9:56 am
Koen Verbeeck (6/4/2012)
Imran Ashraf-452633 (6/4/2012)
On your link provided it is stating something different.http://msdn.microsoft.com/en-us/library/hh479588.aspx
The objects that are stored in the SSISDB catalog include projects, packages, parameters, environments, and operational history.
There's a difference between storing something and versioning something.
There's a lot of items stored on my hard drive, but none of them are versioned.
I know nothing about SSIS and catalog (ya, I know: "go back to school") and I don't think that "versioning" has a word in french 🙂 so, for people like me, if there's any, is there a fast way to explain all that? because from what I understand, the question today was about SQL server storing versions of projects (wich project?) in a database called SSIS? :crazy:
June 4, 2012 at 4:49 pm
Thanks for the question about a new feature.
June 4, 2012 at 5:43 pm
link that states "In this release, only versions of projects are supported in this view."
June 4, 2012 at 7:54 pm
Good straightforward question. Thanks for submitting.
http://brittcluff.blogspot.com/
June 4, 2012 at 11:16 pm
L' Eomot Inversé (6/4/2012)
The catalog.packages view holds version_minor, version_major, and version_build for each package, which seems to make packages pretty well versioned. It also holds version_comments with comments for a specific version of the package, and version_guid which is a globally unique identifier for the specific version of the package. In addition it holds package_format_version to tell us whether this is a version used for SQL2005, SQL2008, or SQL 2012. So I don't believe the idea that packages are not versioned in SSISDB holds water.Environments are apparently not versioned.
Projects are versioned, albeit in a pretty limited manner; the catalog.projects view holds version_lsn and project_format_version, no major/minor version (also no build version, but that's probably irrelevant for a project).
The SSISDB database clearly has versioning for two of the three objects mentioned.
None of the offered answers appears to be correct.
If the question had been "which object types are versioned in the SSISDB catalog view catalog.object_version" the "correct" answer would actually have been correct, but the question was something very different and the correct answer was wrong.
The major/minor version are properties from Visual Studio if I'm not mistaken.
So it's not the SSISDB that performs the versioning, but you yourself in Visual Studio. Also, you don't have the ability to go into the SSIS catalog and say "give me the previous major version of this package". You can only do that in Visual Studio if you have source control set up.
The build number is a number that is incremented every time you save a package in SSDT/BIDS. This was already the case for SSIS 2005/08 and this property was in the previous versions also saved to SSIS, but again, aside from watching it's value, you could do nothing with it.
Projects however, are versioned inside the SSIS catalog and you can perform actions on it.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply