Editing a previously saved package

[sodakotahusker]

I ran the import wizard - saved the package but now I can't find it so I can even run it again. Do I have to make any changes to this guy in Visual Studio? I was trying to make this as simple and painless as possible.

 

[mrdenny]

It's probably saved within the msdb database. Connect to your Integration Service within the Management Studio GUI. From there you should be able to export the package, and bring it into a Visual Studio project. From there you can edit it.

SSIS is a two GUI system now. Management Studio to manage the server, package and schedule and Visual Studio to edit the package.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[sodakotahusker]

I was afraid of that. Oh well. Steep learning curve here I come!
Thanks, Denny!

 

[MDXer]

An additional note is that the Package is only in MSDB if this was the selected deployment. in SSIS you have the option of a File System Deployment if you deploy as a File System package then you can go straight to the directory and grab the file. This type of deployment is really nice as changes to the package simply need to be copied to the SSIS directory where the packages are run from.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck

 

[sodakotahusker]

I had put these in the database. I have now gotten into using VS Integration services. This is really cool. I am developing on one machine with a certain location for text files being imported and a certain server - both of which will change when I deploy to the client.
I used the Wizard to create the packages.
How can I set a variable and use that for all the packages instead of having hard coded connections in each one - both for source and destination.
This really wasn't that difficult to transition to from DTS. I like it!!

 

[MDXer]

use package configurations. this will allow you to set connection properties and variable values. You can save these to either an XML file (which can be a total pain if you have numerous properties), or you can use SQL Server. If you use SQL Server you will have to specify:
1) Connection
2) Database
3) Table. It will create a table for you the first time.

Now number 1 can be an issue as the connection will need to change between enviroments. the way you accomplish this is to:
1) Create a New Datasource that points to the DB that houses your config Table. (I usually call this Config)
2) Create a Package configuration for this Datasource.
3) Make this use the XML option. THis will create a xml config file. This file MUST be located in the same location between enviroments.
4) Make this config the first one in the list.

All other configs can now use this or another connection that points to the same DB where the config table is housed.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck