SQL Server Performance

  • Home
  • Articles
  • Forums
  • Tips
  • Training
  • FAQ's
  • Blogs
  • Software
  • Books
  • About Us
RSS Feeds
Sign in | Join


Article Topics

All Articles
Performance Tuning
Audit
Business Intelligence
Clustering
Reporting Services
SQL Azure
Developer
General DBA
ASP.NET / ADO.NET
SQL Azure

USEFUL SITES :

ASP.NET Tutorials
Windows and SQL Azure Tutorials
Cloud Hosting Magazine
SharePoint Tutorials
Windows Server Help

Write for Us

Share your SQL Server knowledge with others and raise your profile in the community More...
Latest Articles

A High Level Comparison Between Oracle and SQL Server - Part ...
A High Level Comparison Between Oracle and SQL Server - Part ...
A High Level Comparison Between Oracle and SQL Server - Part ...
A High Level Comparison Between Oracle and SQL Server

More     
 
Latest FAQ's

Add Node to A SQL Server failover Cluster failed with invalid ...
SQL Server Destination remote server error
Setting Up Data And Log Files For SQL Server
Will Check Constraints Improve Database Performance?

More     
   
Latest Software Reviews

dbForge Review
Spotlight on ApexSQL Diff - Server-based database comparison tool ...
Spotlight on ApexSQL Data Diff - Server-based database comparison tool ...
Spotlight on ApexSQL Doc 2008

More     

articles >> business intelligence >> Exporting SSIS Package Using SQL Server Management ...

Exporting SSIS Package Using SQL Server Management Studio

By : Ashish Kumar Mehta
Dec 23, 2008

Database Administrators sometimes need to export SQL Server Integration Services Package (SSIS) from one instance of SQL Server to another SQL Server Instance or a File system or a SSIS Package Store. In this article you will see the steps which you need to follow in order to export a SQL Server Integration Services Package that is stored as a File System in an instance of SQL Server to another SQL Server or a File system or a SSIS Package store using SQL Server Management Studio (SSMS).

Different Methods for Exporting SSIS Packages from SQL Server
The most commonly used methods for exporting SQL Server Integration Service (SSIS) Packages from SQL Server 2005 or in SQL Server 2008 are:

 

  • Using Export Package in SQL Server Management Studio (SSMS)
  • Using DTUTIL Command Prompt Utility

 

However in this article you will see how to use Export Package in SQL Server Management Studio (SSMS) to export SSIS package.

Using Export Package in SQL Server Management Studio (SSMS)
You can use Export Package in SQL Server Management Studio (SSMS) to export SSIS packages from three sources such as SQL Server Instance, File System or from SSIS Package Store. In this article we will explore all the three options.

Export Package from File System using SQL Server Management Studio (SSMS)
1. Connect to SQL Server 2008 Integration Services using SQL Server Management Studio.

2. To export an SSIS Package from File System, you need to expand the File System node and then right click the SSIS package which needs to be exported and select Export Package…. from the popup window as shown in the snippet below.


To export an SSIS Package from MSDB, you need to expand the MSDB node and then right click the SSIS package which needs to be exported and select Export Package…. from the popup window as shown in the snippet below 



3. This will open up Export Package dialog box as shown in the snippet below.

 

In Export Package screen you need to select Package Location as “File System” from the drop-down list. However, there are three options available namely SQL Server, File System and SSIS Package Store. When you are selecting File System as an option for the Package location, then it means that you would like to export an SSIS package which is saved as .DTSX file within “Drive:\Program Files\Microsoft SQL Server\100\DTS\Packages” folder. In order to save the SSIS package you need to click “….” button in Package path and provide the folder location where you want the SSIS package to be saved. In this example you will be saving the SalesCustomer.dtsx package to “C:\SSISPackages” location as shown in the above snippet. Here you can even provide a new name while specifying the save location for the package. By default, the Protection Level value for the exported package remains as “Encrypt sensitive data with user key”. If you want to change the protection level then you can choose the appropriate one by clicking “….” button and then finally click OK to export package. Once the package is successfully exported it can be viewed in C:\SSISPackages location.


    Next Page>>    








C# Help and Tutorials | PHP MySQL Tutorial | Sharepoint Tutorial | Azure Tutorial | Cloud Hosting Magazine | ASP.NET Tutorials | Windows Server Help | Windows Phone Pro | Silverlight Ace | Visual Studio Tutorials | Home | Peformance Articles | Audit Articles | Business Intelligence Articles | Clustering Articles | Developer Articles | Reporting Services Articles | DBA Articles | ASP.NET / ADO.NET Articles | SQL Server Training Videos | DBA FAQ's | Developer Peformance FAQ's | DBA Peformance FAQ's | Developer FAQ's | Clustering FAQ's | Error Messages | Audit Tool Reviews | Backup Tool Reviews | Coding Tool Reviews | Compare Tool Reviews | Documentation Tool Reviews | Design Tool Reviews | Monitoring Tool Reviews | Log Tool Reviews | Reporting Tool Reviews | Clustering Tool Reviews | Security Tool Reviews | Change Management Tool Reviews | Remote Access Tool Reviews | Book Reviews | Security Tool Reviews | ADO.NET / ASP.NET | Administration | Analysis/OLAP Services | Application Development | Configuration | Components | ETL | Hardware | High Availability | Hints | Index | Misc | Operating Systems | Performance Tuning | Replication | T-SQL | Views


              © 2010 Jude O'Kelly. All rights reserved