asked
SQL 2012 Job
Hi, On Windows 2003 SQL 2012, I converted 2005 SSIS to 2012 and new project deployment. I deployed the package and ended in `SSISDB\App\Projects\my2012package`. I don't see the package in integration MSDB folder. Kicked off a job (script from 2005 version): @command=N'/DTS "\MSDB\my2012package......and got an error: Could not load package "\MSDB\my2012package" because of error 0xC00060AB. Description: Invalid server name "myserver". SSIS service does not support multi-instance, use just server name instead of "server name\\instance". What did I do wrong? Is there script to deploy the package? Thanks. Chris
Several things to consider: 1. In SSIS 2012 Project Deployment mode, packages are not deployed into MSDB but in to Intergration Services Catalog (SSISDB). You cannot see the packages in msdb. 2. If you want to use a script to launch SSIS 2012 package, you have to point to proper version of DTExec. You have to point to 2012 version of DTExec. Previous version will not work with SSIS 2012 packages. Also you need to point the DTExec to a proper package in SSISDB. See [dtexec Utility][1] 3. In case of using Agent Job, then to launch SSIS 2012 package deployed into SSIS catalog, you have to create a "SQL Server Integration Services Package" job step a as package source you have to specify "SSIS Catalog". Then browse for appropriate package on appropriate server. 4. You can also use a T-SQL to launch SSIS 2012 project deployed package. Easiest way to launch it using T-SQL is browse the package in Integration Services Catalog, Right-Click, choose execute, set all necessary parameters and then Click the Script Button in the top of the dialog. This will generate a T-SQL Script for the package execution. Only take in to account, that Project Dpeloyed packages (deployed into SSISDB) are executed on the server hosting the SSIS Catalog. Even when executed using the DTExec command line utility. [1]:
http://technet.microsoft.com/en-us/library/hh231187.aspx
16 People are following this question.
