A commit failed

  • Is it possible to give all the exact error messages?

    Maybe you could try to write the updates to a staging table and do the updates after the data flow in an Execute SQL Task.

    That way you avoid the OLE DB Command, you work with a set based approach and you avoid possible concurrency on your destination table.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Thanks.

    The error message is

    [SQL Server Destination [794]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)".". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "The OLE DB provider "BULK" for linked server "(null)" reported an error. The provider did not give any information about the error.". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Reading from DTS buffer timed out.".

    [SQL Server Destination [794]] Error: A commit failed.

    You might be right, I just try to avoid another staging table.

  • Are you trying to access data from a linked server?


  • No, I do not have a linked server. All INSERTS and UPDATES are aiming to the same table/database/server/machine.

    Thanks.

  • Is the Integration Services service running on the same server as the destination table?

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Everything on the same box.

    Thanks.

  • I am facing same problem.What was the solution for this problem.

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

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