Modify SSIS package saved on server

Modify SSIS package saved on server

• daniel qi

  Naturally you can import the package from the server into your solution, edit the package in the solution + test and then save to server.
  

• Luke_Adams

  As Craig pointed out we do not enable editing of deployed packages. This is to keep a clear distinction between packages still in development and packages which are tested and in production.

  The best practice would be do work in the development environment then when complete and tested move production copies to the server by deploying them. When changes have to be made, they are made to the original development packages in the dev environment - once tested, copies of the modified packages would then be deployed to the server over the existing production packages.

  As you have found, it is still possile to use the Import/Export wizard in the development environment for convenience.

  However, some users have simpler scenarios - they build quick packages for simple import/export jobs and save them directly to the server. For such scenarios, it may be easier simply to run the wizard again with new options and deploy new versions to the server - certainly some administrators prefer this simpler approach to working in the development environment.

  You may have a third case, where you have created packages in the wizard, and need to make changes to them that cannot be accomplished simply by running the wizard again - perhaps introducing some logic that the wizard does not cover. In such a case, use the Export option in SQL Server Management Studio (right click in the Object Explorer for Integration Services should have that option) to save a server package to the file system. Now, in the BIDS environment, you can start an SSIS project and using Add Existing item, you can add the file system package to your project.

  This last case is really only worth the effort if (a) you have logic that cannot be supported in the wizard and (b) you wish to follow the develop-test-deploy practices. For many simple admin cases, where SSIS is being used just an import / export utility, it would be easier just to run the wizard again and deploy new packages.

  hth

  Donald Farmer

  
  
  

• Oroborus

  Werener.. thanks for the reply. I am assuming by your post you mean that I have to use VS2005, Business Intelligence Dev Studio I did see what you mean by importing it. Thank you.

  Jim

  
  
  

• chicoamaral

  OK! Everything understood. In DTS 2000 you can see the package in the left menu. In 2005 you can't. Or maybe I do something wrong when i import the package to Mgm Studio There are 2 methods to import: file system and sql server. I tried to import inside the sql server (because I was thinking I can see it after in the menu, but ...) and run a job every day for this package. Problem: My job don't run or run with "Package can't be found or loaded" error.

  Any ideea

  
  
  

• sdsachs

  sorry, no. Currently you cannot load a package from Mgt studio for editing. From Mgt studio you can see whats running, whats stored, and can execute a package but not edit.

  
  
  

• ejaz

  I really miss good ole DTS packages. The old days when you could write a process and edit it without running through a ton of unnecessary hoops. Microsoft is a tools provider. It is NOT Microsoft's place to say HOW we use the tools. Keeping a clear distinction between development and product is something that I am supposed to make decisions on without being told that I have to do it a certain way.

  Your response to "hey, this is needlessly complicated and well, stupid." is "it may be easier simply to run the wizard again with new options and deploy new versions to the server - certainly some administrators prefer this simpler approach to working in the development environment." If it wasn't written down I would not believe that you said it.

  SSIS is a definate step back from DTS.

  
  
  

• Al_chan

  How exactly does this work

  After I edit the package in BI studio, the only option is to save it as a file on the file system. And the import/export wizard appears to be for just importing/exporting data. If I right click on the SSIS packages folder in the Solution Explorer, the import/export wizard is the same one for importing/exporting data. There's no data source you can select for SSIS packages.

  This is highly frustrating as any SSIS package I've saved to the server from the Data Import/Export wizard is uneditable at this point.

  
  
• Modify SSIS package saved on server