![]() |
|
|
By: Jeremy Kadlec | Read Comments (1) | Print Jeremy is the CTO @ Edgewood Solutions, co-founder of MSSQLTips.com and SQL Server MVP since 2009. Related Tips: More |
|
Problem
I have seen many of the changes with SQL Server 2005 Integration Services (SSIS) versus SQL Server 2000 Data Transformation Services (DTS). Integration Services certainly has much more functionality out of the box than DTS and I am learning SSIS as my projects move forward. One item that has seemed to be a thorn in my side is deploying an SSIS package. So, I have read your tip (SQL Server Crosswalk - Deploying a SQL 2000 DTS vs. a SQL 2005 SSIS package) related to deploying a package and wanted to find out if any other options are available? Can you shed some light on the situation?
Solution
You are right about SSIS vs. DTS. SSIS certainly has a great deal of functionality out of the box as compared to DTS, but in some respects some of the simpler aspects of DTS Packages have been over shadowed by a standardized development platform (Business Intelligence Management Studio) with SSIS. The net result is for the sake of new technology, new processes are needed. One of those items could be considered the deployment of an SSIS Package with the deployment manifest wizard. In the SQL Server Crosswalk - Deploying a SQL 2000 DTS vs. a SQL 2005 SSIS package tip we talked about creating a deployment manifest file and using that file for deployment purposes. Let's also outline another approach in this tip which is using Management Studio to import or export an SSIS Package.
Deploying an SSIS Package
Although the detailed steps for deploying an SSIS Package are outlined in this tip (SQL Server Crosswalk - Deploying a SQL 2000 DTS vs. a SQL 2005 SSIS package) let's outline the general steps:
As you can tell, this is a much different process as compared to the SQL Server 2000 DTS Packages where all of the development and deployment was directly in Enterprise Manager.
Importing an SSIS Package in Management Studio
As compared to the process above, importing an SSIS package via Management Studio may be considered a much simpler approach. Let's walk through the process of importing the SSIS Package via Management Studio once the package is saved in BIDS.
|
Import a SQL Server Integration Services Package in Management Studio |
Import Process - In order to start the SSIS import process follow these steps:
|
|
|
Import Package Options - Below outlines the interface options:
|
Exporting an SSIS Package in Management Studio
Since we covered importing an SSIS Package with Management Studio, let's also cover exporting an SSIS package with Management Studio:
|
Export a SQL Server Integration Services Package in Management Studio |
Export Process - In order to start the SSIS export process follow these steps:
|
|
|
Export Package Options - Below outlines the interface options:
|
Delete an SSIS Package in Management Studio
The deletion process in Management Studio is very straight forward. Just right click on the package and select the 'Delete' option.
Save Copy of Package in Business Intelligence Development Studio
|
Save Copy of Package in Business Intelligence Development Studio (BIDS) |
Save Copy of Package Process - In order to start the process follow these steps:
|
|
|
Export Package Options - Below outlines the interface options:
|
Command line management with dtutility
Although the Management Studio and Business Intelligence Development Studio offer rich interfaces to manage SSIS Packages, Microsoft also offers the option to copy, move, delete, or verify the existence of an SSIS Package with the dtutil command. This alternative may prove priceless if you are faced with a situation where you need to manage large numbers of SSIS Packages in an automated manner. Here are some simple coding examples with the dtutil command:
|
Copy and rename the SampleSSISPackage to Export_FlatFile_Daily_CustomerData.dtsx |
| dtutil /FILE c:\DevSSISPackages\SampleSSISPackage.dtsx /COPY FILE;c:\TestSSISPackages\Export_FlatFile_Daily_CustomerData.dtsx |
|
Move the 'SampleSSISPackage' from Package Store to the MSDB database |
| dtutil /DTS SampleSSISPackage.dtsx /MOVE SQL;SampleSSISPackage |
|
Delete the SSIS Package named 'SampleSSISPackage' in the MSDB database |
| dtutil /SQL SampleSSISPackage /DELETE |
|
Verify the SSIS Package named 'SampleSSISPackage' in the MSDB database |
| dtutil /SQL SampleSSISPackage /EXISTS |
The sample code in this tip for the dtutil command is only the tip of the iceberg. For additional information about the dtutil command visit - dtutil Utility.
Next Steps
| Share: | Share | Tweet |
|
![]() |
![]() |
Free SQL Server Learning |
| Monday, February 14, 2011 - 1:34:43 AM - Vikash Kumar Singh | Read The Tip |
|
Nice article. Good info on DTUTIL. |
|
|
privacy | disclaimer | copyright | advertise | about authors | contribute | feedback | giveaways | user groups Some names and products listed are the registered trademarks of their respective owners. Edgewood Solutions LLC | MSSharePointTips.com | MSSQLTips.com |