Post reply

SSIS job failed to run in SQL server agent

  • July 31, 2011 at 9:15 pm

    #245274

    we created SSIS import package, it worked fine but the scheduled job failed to run after a column added. The column mapped to LoanNo in SSIS but the sql agent job failed to run and the error message as below:

    The job history shows :cannot insert value NULL into the column 'LoanNO' Table xxx column doesn't allow NULL ....

    I am new to SQL programming. I am not sure how to fix this?

  • August 1, 2011 at 12:29 am

    #1361371

    Hi,

    can you try running the package in BIDS ( Business Intelligence Develeopement Studio) ? When you added the new column to the table you would have kept it as NOT NULL, and while importing value to the table it looks like some NULL values is coming.

    So check the property of the column and the values which is coming to that column while you do the import.

    Thanks & Regards,
    MC

  • August 1, 2011 at 3:08 am

    #1361405

    If you don't have a value for this new column in your existing source file, you can use some default value for that column.

    If you don't want to change SSIS, just add default for the 'LoanNO' column in your xxx table itself. If the query in SSIS doesn't use "select * ..." everything should work.

    _____________________________________________
    "The only true wisdom is in knowing you know nothing"
    "O skol'ko nam otkrytiy chudnyh prevnosit microsofta duh!":-D
    (So many miracle inventions provided by MS to us...)

    How to post your question to get the best and quick help[/url]

  • August 1, 2011 at 9:23 pm

    #1361947

    Later we found out we don't need to change any value. We just removed the package from SQL Intergrated services and re-add it back then it works.

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

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