<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Deploy SSIS 2012 projects using catalog.deploy_project Stored Procedure</title><link>http://blogs.msdn.com/b/mattm/archive/2012/12/06/deploy-ssis-2012-projects-using-catalog-deploy-project-stored-procedure.aspx</link><description>In SQL Server 2012, you can use the catalog.deploy_project stored procedure to deploy an SSIS project to the SSIS server. You need to provide the binary contents of the project deployment file (.ispac extension), for the @project_stream parameter, along</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Deploy SSIS 2012 projects using catalog.deploy_project Stored Procedure</title><link>http://blogs.msdn.com/b/mattm/archive/2012/12/06/deploy-ssis-2012-projects-using-catalog-deploy-project-stored-procedure.aspx#10380875</link><pubDate>Thu, 27 Dec 2012 02:50:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10380875</guid><dc:creator>Carla Sabotta</dc:creator><description>&lt;p&gt;Hi Koen,&lt;/p&gt;
&lt;p&gt;Yes, you can deploy projects from server to server using the catalog.deploy_project stored procedure. &lt;/p&gt;
&lt;p&gt;You create a Linked Server object to a SQL Server instance and configure it to enable RPC and RPC Out, and set Enable Promotion of Distributed Transaction to False (Server options page of the Linked Server Properties dialog). And, be sure to enable Dynamic Parameters for the provider selected for the Linked Server object; to enable it, right-click the provider under the Providers node (under Linked Servers in Object Explorer), and then click Properties. &lt;/p&gt;
&lt;p&gt;Call catalog.get_project to return the binary for the project and then call catalog.deploy_project. &amp;nbsp;In the following example, &amp;nbsp;catalog.get_project returns a binary for the MySSISProject project on the linked server. The value is inserted into a table variable of type varbinary(max); the linked server can&amp;#39;t return results that are varbinary(max). The catalog.deploy_project deploys the project to the local server, to the folder named DestFolder.&lt;/p&gt;
&lt;p&gt;declare @resultsTableVar table (&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; project_binary varbinary(max)&lt;/p&gt;
&lt;p&gt;)&lt;/p&gt;
&lt;p&gt;-- Insert the results into table variable&lt;/p&gt;
&lt;p&gt;-- Linked server cannot return results that are varbinary(max)&lt;/p&gt;
&lt;p&gt;-- To do the steps below, Enable RPC/RPC-out for the linked server&lt;/p&gt;
&lt;p&gt;INSERT @resultsTableVar (project_binary)&lt;/p&gt;
&lt;p&gt;EXECUTE [MyLinkedServer].[SSISDB].[catalog].[get_project] &amp;#39;MyFolder&amp;#39;,&amp;#39;MySSISProject&amp;#39;&lt;/p&gt;
&lt;p&gt;declare @project_binary varbinary(max)&lt;/p&gt;
&lt;p&gt;select @project_binary = project_binary from @resultsTableVar&lt;/p&gt;
&lt;p&gt;-- Deploy to SSIS Catalog&lt;/p&gt;
&lt;p&gt;exec [SSISDB].[CATALOG].[deploy_project] &amp;nbsp;&amp;#39;DestFolder&amp;#39;,&amp;#39;MySSISProject&amp;#39;,@project_binary&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10380875" width="1" height="1"&gt;</description></item><item><title>re: Deploy SSIS 2012 projects using catalog.deploy_project Stored Procedure</title><link>http://blogs.msdn.com/b/mattm/archive/2012/12/06/deploy-ssis-2012-projects-using-catalog-deploy-project-stored-procedure.aspx#10375969</link><pubDate>Mon, 10 Dec 2012 07:06:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10375969</guid><dc:creator>Koen Verbeeck</dc:creator><description>&lt;p&gt;I&amp;#39;m guessing this can be used as well to deploy projects from server to server? I&amp;#39;ll have to test it out, but that would be awesome.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10375969" width="1" height="1"&gt;</description></item><item><title>re: Deploy SSIS 2012 projects using catalog.deploy_project Stored Procedure</title><link>http://blogs.msdn.com/b/mattm/archive/2012/12/06/deploy-ssis-2012-projects-using-catalog-deploy-project-stored-procedure.aspx#10375371</link><pubDate>Thu, 06 Dec 2012 20:49:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10375371</guid><dc:creator>ArthurZ</dc:creator><description>&lt;p&gt;I think this a very useful example on how to automate (or script) SSIS project deployments; also this is suited to using this approach together/within the SSDT for activities as scripting tables, data, etc. to promote a project as one monolithic unit.&lt;/p&gt;
&lt;p&gt;Just another reason to preach to upgrades to SSIS 2012.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10375371" width="1" height="1"&gt;</description></item></channel></rss>