SSIS load and backup conflice

  • I have a nightly database load that is triggered by some processes outside of my control. This normally runs with no problems, but occasionally I am getting a conflict with an hourly tlog backup that is occurring on the server.

    The first step in my package truncates some tables and the next step starts loading data.

    I am getting an error message in the log that says:Process ID 67 was killed by hostname SQLDW, host process ID 5252

    My actual SSIS error says a primary key was violated - duplicate was entered. I have verified that there are no duplicates in the input flat file, so I believe that the truncate is not actually wiping out the contents of the table. I think the truncate may be having blocking issues with the tlog backup.

    Is there any way to verify what I think is happening? And more importantly, is there any way to correct this? I would really like for my ssis project to wait until the backup is complete (or vice-versa) instead of failing. Any suggestions?

    Thanks,

    Kim Talley

Viewing post 1 (of 1 total)

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