Post reply

Saving a package from a Structured Storage File over an existing package causes error due to different Package ID

  • October 4, 2005 at 5:08 am

    #165795

    I have a query. I use Structured Storage Files to transfer packages between servers but if I am replacing an original package with an updated version I get a packageID mismatch error if I try to save over the original package. How can I save the new version on the server whilst retaining the original versions.

     

    Thanks in Advance

    JB

  • October 4, 2005 at 6:50 am

    #594801

    Maintain the versions in something like Sourcesafe, not in SQL Server. Although the package designer does create different versions there is not facility to rollback changes, or as you've found out apply "updates". Plus it has a rather annoying habit of creating new versions every time you save even if you haven't made any changes.

    An approach I use that doesn't use storage files is,

    1. Make dev package ready for deployment ( delete old versions, dev server references, etc... )

    2. Backup package on Prod using DTSBACKUP 2000

    3. Remove package from Prod

    4. Transfer package from Dev to Prod using DTSBACKUP 2000

    If you must use storage files then here's another approach,

    1. Save latest Dev version to storage file with unique name and place in Source Control.

    2. Save current Prod package to storage file and save in archive or source control ( whichever is appropriate ).

    3. Remove package from Prod server.

    4. Open file created in step 1 and save to server.

     

    --------------------
    Colt 45 - the original point and click interface

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply