Post reply

Scheduling a SSIS package

  • April 16, 2008 at 12:10 am

    #124867

    Hi All,

    How we schedule a SSIS package in SQL Server Agent JOb

    can anybody tell the process

    thanks

    sathish

  • April 16, 2008 at 6:13 am

    #803020

    - Create a job

    - Add a step

    - Choose the step type for executing an SSIS package

    - Select the package you want to run

    The UI is fairly intuitive, you may want to just try it.

  • April 16, 2008 at 6:31 am

    #803037

    Thanks Michael,

    yesterday i have tryied in the same way how you told, job is created successfully, but it is not executing at the specified time.

    what is the problem?

    thanks

    sathish

  • April 16, 2008 at 8:23 am

    #803112

    Check the job log (assuming it's actually erroring), also check to ensure SQL Agent is actually running.

    Steve.

  • April 17, 2008 at 2:44 am

    #803526

    You need to create a schedule from the schedule tab for the job to execute at the specified time.

    Make sure you check the Enabled checkbox in the schedule tab.

    Regards,

    Samata

  • April 30, 2008 at 4:47 am

    #808918

    Thanks samata,

    The Enabled checkbox is checked, the job execution is failed.

    The message in View History is like

    Message

    The job failed. The Job was invoked by Schedule 17 (NewJob1). The last step to run was step 1 (Step1).

    so where iam doing mistake actually.

    pls give me any suggestions

    Thanks

    sathish

  • May 26, 2008 at 5:41 am

    #820173

    Hey Satish,

    On the job history, click on the expand (+) button, and look at the history for the specific step.

    Looking at the history for the job isnt going to give you much, the actual reason for failure is more likely to reside at a step level.

    The first thing I would ask is if my SQL server agent has the correct access required by the package.

    ~PD

  • May 26, 2008 at 7:27 am

    #820187

    In your SSIS package you can also create a log.

    Use this log to document all the steps that your package runs through, and check the log verifies everything correctly by running the package manually through BIDS.

    The next step (instead of a scheduled run) is to force the job to run through sql agent by starting it manually. Check the log for more details if the job fails, as this will give you more insight into exactly what the failure is. If the job does fail here, it's often down to security settings which haven't been configured correctly.

Viewing 8 posts - 1 through 7 (of 7 total)

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