DTS running while transaction locks a table

  • We have a situation where a DTS package runs at 8:30pm every night.

    Every once in a while a get a user saying that his data was not saved, at the log always shows this to be at 8:30 pm.

    Our DTS package imports large text files into tables that are being used by users at the same time. Some of the functions that users trigger (during saving) are transactions (BEGIN, COMMIT, etc).

    Can it be that some transactions don't execute properly because a DTS is using the table?

    Thanks !

  • I can several things potentially in play here..

    1. The load of data can affect the locking of those tables, a lot depends on the options you have selected in the datapump.

    2. Transactions could certainly be delayed due to locking but they either fail or succeed, there is no middle ground.

    3. Also there is the possibility of deadlocks. And connections that don't have a lot of IO and such usually are the deadlock victims.

    4. Is it possible that the data loading could overwrite a change from the transaction?

    These are just the things that came to mind.

    CEWII

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

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