Finding the origins of a SSIS package

  • Hello

    I have inherited a few SSIS packages along with some jobs that run them.

    I am able to find the packages behind pretty much every SSIS package as they're held within 2 projects that I can edit within visual studio.

    One of the packages seems to be missing and looks to have been generated using a different method.

    I can see that it runs as pat of a job.

    The job makes a call to SQL Server for the package source rather than SSIS Catalog.

    It makes reference to the package location.

    So, if I open SSMS and connect to SSIS

    Then drill down through Stored Packages and MSDB, I can see it

    I just cannot get at the package to see what it does or amend it

    Any thoughts as to how this was generated?

    Thanks

    Damian.

    - Damian

  • DamianC (8/19/2015)


    Hello

    I have inherited a few SSIS packages along with some jobs that run them.

    I am able to find the packages behind pretty much every SSIS package as they're held within 2 projects that I can edit within visual studio.

    One of the packages seems to be missing and looks to have been generated using a different method.

    I can see that it runs as pat of a job.

    The job makes a call to SQL Server for the package source rather than SSIS Catalog.

    It makes reference to the package location.

    So, if I open SSMS and connect to SSIS

    Then drill down through Stored Packages and MSDB, I can see it

    I just cannot get at the package to see what it does or amend it

    Any thoughts as to how this was generated?

    Thanks

    Damian.

    It would have been generated as usual, but individually deployed using the package-deployment model. Perhaps the original project got lost & only the package remains.

    If you want to 'get at the package', just add it to an SSIS project (right-click on project in Solution Explorer and Add / Existing Package).

    Once you have done this, you'll be able to open it.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Excellent, works perfectly

    Thanks

    - Damian

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

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