Post reply

SSIS

  • November 14, 2007 at 6:47 pm

    #121112

    Hi

    We use SSIS packages to populate tables in sql server 2005.

    We have a job running for 2 years with no problems.I had to add a column to one of the tables.I added it and deployed it to the sql server.When I run the job manually,it works fine anf the new column is populated.When the job runs under schedule,only the column that was newly added(date column) becomes null and everything else is fine.

    Any suggestion will be helpful.

    thanks

  • November 15, 2007 at 2:06 pm

    #751645

    anybody...any idea.....

  • November 15, 2007 at 2:17 pm

    #751650

    Are you certain the schedule is referring to the same stored SSIS project?

  • November 15, 2007 at 6:01 pm

    #751686

    Yes I am..when I delete the particular package from Integration services,the job fails at the step.It is running the same package but is ignoring the changes made to it...

    I tried restarting the sql server agent and also the Integration services.It worked the first time and then failed to populate the newly added column.

    This is really a weird problem which i have never encountered before.

    I am stuck on this as the job is running every two hours,I go run the package manually at sql server to populate the column after every job run.This is really a pain.Any suggestion would be helpful.

    Thanx

  • November 16, 2007 at 7:51 am

    #751848

    Have you tried changing the GUID in the SSIS package properties and the name that you use when you load it into msdb? (Try adding a build number).

  • November 16, 2007 at 8:47 am

    #751875

    Basically what you have done here is getting the job running from the old ssis package path.

    Here is what you need to do:

    1. File>save copy of.......as(give a new path at the bottom)

    2. Go to Management Studio,create a new job, step, schedule

    3. say OK and test it by right clicking on job, start step as

    4. If both rows are green, your package will now run successfully at the set schedule.

    Good Luck!

    ........Jasmeet

    [font="TimesNewRoman"] “I haven't failed, I've found 10,000 ways that don't work”........Thomas Alva Edison[/font]

  • November 25, 2007 at 2:53 pm

    #753831

    Hey guys

    Thanks for the post.This has finally been solved.

    The problem was that ,my boss had run the same job at the same schedule at another server.So,both the jobs were running at the same time.the newer deployed version and the old one from other server.He was on vacation and finally when he came back,he disabled it and things worked. He had forgotten to disable it when he left.Thanks to you all....It definitely was a great learning experience....

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

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