Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- conflict-free SQL statements
- Oliver Spiesshofer
December 7, 2004, 6:56 pm
rate this thread
I am running a script that reads a large amount of data from a ODBC-Link
into a new table, then deletes a target-table and copies the new table into
I often get corrupt results that can be recovered by repairing the table.
I assume that the second process starts before the first has finished.
Any idea how to prevent this? Do I have to lock the tables? I know that no
other process is writing into the tables however.