This project has moved and is read-only. For the latest updates, please go here.

Analysis doesn't support SSIS DB Catalog


This was added to a closed issue:

I am using SQL 2012 and store my packages in the new SSISDB catalog. When I select the server name containing this new SSIS catalog, the dependency executor is still attempting to enumerate the SSIS package from the OLD AREA in SQL SERVER and not the new "Integration Services Catalogs" area (SSISDB)

I know this because the output window tells me this:

Loading SQL package '\Data Collector\SqlTraceUpload'... Error occurred: 'The variable cannot be found. This occurs when an attempt is made to retrieve a variable from the Variables collection on a container during execution of the package, and the variable is not there. The variable name may have changed or the variable is not being created.
Loading SQL package '\Data Collector\TSQLQueryCollect'... Completed Successfully.
Loading SQL package '\Data Collector\TSQLQueryUpload'... Completed Successfully.
Loading SQL package '\BTSDESQL110\DTS Packages\Copy Database Wizard Packages\CDW_BTSDETSTSQL24_BTSDESQL110_0'... Completed Successfully.
Enumerating Analysis Services metadata.

Am I doing something wrong?


kmartin wrote Sep 30, 2015 at 2:13 PM

This is looking to be very difficult to achieve.
Microsoft have not provided the equivalent of "LoadFromSqlServer" or "LoadFromDtsServer" with the Package Catalog.
You have to use GetProjectBytes to download the ispac, run it through an unzip, get the packages out of it, and then run those though as files.
Got a bunch more code to do to make this possible.

Mirsky72 wrote Sep 6, 2016 at 8:49 PM

How about this? Since I have this in source control, why don't I just point to the locally mapped drive to which my TFS objects are mapped!?? As a workaround, that is?

wrote Jan 10 at 2:16 PM