Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

package opens up as xml file Expand / Collapse
Author
Message
Posted Monday, September 02, 2013 5:38 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 8:11 AM
Points: 221, Visits: 860
Hi
I am quite new to SSIS and I am having the following problem.
I want to open the ssis package locally on my laptop to take a look at the current steps/tasks and control flow that the job currently implements. On the general tab of the job (which i open the server) i can see under Package that it is stored in:
\MSDB\FolderA\DataFeeds\datafeedGeneric and under the Configurations tab i can see S:\SSIS\Datafeeds\ClientName\ClientName.dtsConfig

I have copied the file with the .dtsConfig extension from the server to my laptop locally and tried to open it in bids but it opens in xml.
Am i correct in saying i need to locate a file with .dtsx extension ?
Do i need to get the package from the msdb location ie the MSDB\FolderA\DataFeeds\datafeedGeneric and if so how do i go about this.
I have some other questions too but i'll raise a new thread for those
Post #1490591
Posted Monday, September 02, 2013 6:46 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: 2 days ago @ 7:48 AM
Points: 1,533, Visits: 7,916
Yes, the DtsConfig file contains parameters for the SSIS package - it is one way of making the package more flexible by changing parameters instead of rebuilding the SSIS package every time you want to change a value.

There are several ways to open the the actual SSIS package (the dtsx file).
One way is to open Visual Studio, create a new SSIS project and then, in the Solutions Explorer, right-click on 'SSIS Packages' and select 'Add Existing Package'. from this dialog you can select the Server and then the package you want to import.

You can also connect to the Integration Services Server via SSMS, right click on the package under 'Stored packages/MSDB' to locate your SSIS package. then right-click on it and select 'Export Package...' to save it as a file or even move it to another IS Server.



BrainDonor
Linkedin
Blog Site
Post #1490607
Posted Monday, September 02, 2013 6:51 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 8:11 AM
Points: 221, Visits: 860
There are several ways to open the the actual SSIS package (the dtsx file).
One way is to open Visual Studio, create a new SSIS project and then, in the Solutions Explorer, right-click on 'SSIS Packages' and select 'Add Existing Package'. from this dialog you can select the Server and then the package you want to import.


If i implement this method will it in any way effect the live package on the server . ie if I where to play around with the package on my local laptop after exporting will it effect things live - does the live package still remain 'as is' on the live server ?
Post #1490609
Posted Monday, September 02, 2013 6:57 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: 2 days ago @ 7:48 AM
Points: 1,533, Visits: 7,916
PearlJammer1 (9/2/2013)
There are several ways to open the the actual SSIS package (the dtsx file).
One way is to open Visual Studio, create a new SSIS project and then, in the Solutions Explorer, right-click on 'SSIS Packages' and select 'Add Existing Package'. from this dialog you can select the Server and then the package you want to import.


If i implement this method will it in any way effect the live package on the server . ie if I where to play around with the package on my local laptop after exporting will it effect things live - does the live package still remain 'as is' on the live server ?


When you import it this way, once opened you only have the option to 'Save As...', so you can't overwrite the installed package by mistake.

If you want to feel really safe, just export it from the IS server instead, that will create a dtsx file where you specifiy and then there is no doubt it isn't the server's copy.


BrainDonor
Linkedin
Blog Site
Post #1490611
Posted Monday, September 02, 2013 8:12 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 8:11 AM
Points: 221, Visits: 860
You can also connect to the Integration Services Server via SSMS, right click on the package under 'Stored packages/MSDB' to locate your SSIS package. then right-click on it and select 'Export Package...' to save it as a file or even move it to another IS Server.


Ok Just clarify 100% before I do this.
I have connected to ssis from ssms and located the package as you mentioned above. So just to clarify, 'exporting' doesnt remove the package from this location - it is in effect just like copy and paste at a simple level - so the package actually stays on the server and performs as nothing has happened ??

Sorry for the hesitation on this, its just the first time i have done this.....
Post #1490633
Posted Monday, September 02, 2013 8:57 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: 2 days ago @ 7:48 AM
Points: 1,533, Visits: 7,916
PearlJammer1 (9/2/2013)
You can also connect to the Integration Services Server via SSMS, right click on the package under 'Stored packages/MSDB' to locate your SSIS package. then right-click on it and select 'Export Package...' to save it as a file or even move it to another IS Server.


Ok Just clarify 100% before I do this.
I have connected to ssis from ssms and located the package as you mentioned above. So just to clarify, 'exporting' doesnt remove the package from this location - it is in effect just like copy and paste at a simple level - so the package actually stays on the server and performs as nothing has happened ??

Sorry for the hesitation on this, its just the first time i have done this.....


Not a problem - I don't like the first time I do anything regarding SSIS!

Yes, it will save a copy of the package to your specified location and leave the installed package on the server. You can then edit the saved package/file without any impact on the package stored on the server.


BrainDonor
Linkedin
Blog Site
Post #1490644
Posted Monday, September 02, 2013 9:48 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 8:11 AM
Points: 221, Visits: 860
Thanks for all your help.
I can now look at the package in BIDS !!
Brilliant - thanks
Post #1490659
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse