Post reply

Creating a Manifest file

  • July 22, 2009 at 3:27 am

    #136382

    I have created a package in SSIS

    That updates a SQL table from MS Access every time i run it, which works fine

    What I would like to do it to add the SSIS package to the Job list so it automatically runs (scheduling)

    I’ve been told that I need to create a manifest file first? Then what do i do?

    Thanks in advance

  • July 22, 2009 at 4:04 am

    #1028181

    While it may well be your company's policy to do this, it is not mandatory.

    It is perfectly possible to create a SQL Agent job to run a package which exists as a DTSX file in the file system. So if the development of the package was performed on the same server that the package is to be deployed, there is no need for a deployment manifest.

    But if you did the development on a local instance, you will need to transfer your packages to the main server and creating a deployment manifest could help. Select Project/Properties/Deployment Utility and set CreateDeploymentUtility to true. Next time you compile, the utility will be created and can be run on the server to which the package is to be deployed. It's been a while since I used it, so please excuse any slight inaccuracies in my description.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • July 22, 2009 at 5:06 am

    #1028197

    thanks

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

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