Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You can programmatically build SSIS packages using C# or VB.NET and then run the packages. You can also load an existing package programmatically to execute it. I have little experience with building packages this way since most of the packages can be built easily using the following tools.</p> <p>Read the article <a href="http://msdn.microsoft.com/en-us/library/ms345167.aspx" rel="nofollow">Building Packages Programmatically</a> on MSDN for more details.</p> <p>I feel that it is easier to build the packages through these IDEs depending on which version of SSIS you are targeting. You can also create initial packages through SQL Server Import and Export Wizard and save the SSIS packages to the local disk, which you can later modify according to your needs.</p> <pre><code>SSIS Version Development IDE Visual Studio Shell ------------------- ----------------------------------------------- ------------------- SSIS 2005 Business Intelligence Development Studio (BIDS) Visual Studio 2005 SSIS 2008 - 2008 R2 Business Intelligence Development Studio (BIDS) Visual Studio 2008 SSIS 2012 SQL Server Data Tools (SSDT) Visual Studio 2010 </code></pre> <p>You need to reference the appropriate SSIS specific DLLs in your code to create/load SSIS packages. </p> <p>However, you will need a <em><code>SQL Server Integration Services</code></em> license to run the package. You cannot simply reference the DLLs alone. The license is usually part of your SQL Server license, if you already have one.</p> <h3>Response to your comment:</h3> <blockquote> <p>We will have SQL 2012 or 2008R2 on a separate server.. So I just need to paste the needed DLLs on my web server and reference them. correct ?</p> </blockquote> <p>The packages will execute on that server. You are just remotely invoking to execute them and you should reference the appropriate DLLs in the code within your web/other form of external application. I usually schedule the packages to run on the database servers under <em>SQL Server Agent Job</em>. You can try that if that is an option for you.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload