Share via


Open SSIS Package

Question

Thursday, June 7, 2012 11:13 AM | 1 vote

Hi Team,

How many ways to open SSIS package in SQL Server 2008 R2

Tx

subu

All replies (10)

Friday, June 8, 2012 6:41 AM ✅Answered

Hi Subu,

Since you chose to save the package in SQL Server - The Package will be saved in the MSDB Database in SQL Server.

You can access the package from SQL Server Management Studio.

1) Select 'Integration Services' in the connection option instead of 'Database Engine'.
2) Expand Stored Packages - Expand MSDB and search for your package (With the same name which you used during saving the package.)
 
In order to manipulate the SSIS Package ,

1) You could right click on it and Export to a .dtsx file and Open the DTSX file in BIDS / SQL Server Management Studio.
After modification - import the package again to MSDB database by right clicking on the MSDB folder in SSMS (Integration Services) and selecting Import Package option

2)Or you could modify the package without export it to dtsx file. This is what you need to do:
 •Start "Integration Services" on the server.
 •Strart BIDS and open a SSIS project.
 •Click 'Project' in mamu bar and select 'Add existing package' from the pull_down.
 •In the pop-up window, type in the server name, and set the right package path. Then you will be able to work on the package directly. With this way, you may keep the package you change always on server

Best Regards,
Peja

Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


Thursday, June 7, 2012 11:18 AM

BIDS? Open means launch?????

Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/


Thursday, June 7, 2012 11:28 AM

yes, i want to lunch but where i dont know the path.. But when i checked in Management studio i can see the package under MSDN database.

subu


Thursday, June 7, 2012 11:36 AM

http://www.mssqltips.com/sqlservertip/2135/run-ssis-using-xpcmdshell-in-a-sql-server-stored-procedure/

Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/


Thursday, June 7, 2012 12:26 PM

Hi Uri, My package is deployed in MSDN, how i can open the package from BIDS?

subu


Thursday, June 7, 2012 12:29 PM

What does it mean "deployed in MSDN"?????

Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/


Thursday, June 7, 2012 12:53 PM

I mean my package is not stored in Hard disk and its is stored in database

subu


Thursday, June 7, 2012 12:53 PM

Uri, may be he was meant 'MSDB' database.

Subu,

You can launch an SSIS package in many ways:

1. Running from BIDS (by pressing F5 or Ctrl + F5)

2. Using DTExecUI tool

3. Using DtExec command-line utility

4. You can combine xp_cmdshell and DTExec and launch the package from TSQL

5. From custom .NET applications byreferencing Microsoft.SqlServer.Dts.Runtime assembly

Krishnakumar S


Thursday, June 7, 2012 12:59 PM

if its in production we can enable xp_cmdshell..?

subu


Thursday, June 7, 2012 1:24 PM | 1 vote

Explore various options mentioned above and test it thoroughly and select one based on your specific requirement.

You can enable xp_cmdshell in production; If its still not enabled on your production server, I'm not recommending to enable this and use it to launch an SSIS package.

Why We Recommend Against xp_cmdshell

Krishnakumar S