then just make a BATCHMOVE (keep source) to test the time taken. surely less time.
test integrity of data in the Target Table Drop the Old full table. I think a backup and restore will been necessary if there are millions of rows!!! Cheers 2017-07-16 13:53 GMT+04:00 Ertan Küçükoğlu [email protected] [firebird-support] <[email protected]>: > > > > Sent from my iPhone > > On 16 Jul 2017, at 11:58, Alain Bastien [email protected] > [firebird-support] <[email protected]> wrote: > > > > Else *"What's in a NAME?" > <https://www.enotes.com/shakespeare-quotes/what-s-name-that-which-we-call-rose>* > > > > > > > > 2017-07-16 12:47 GMT+04:00 Alain Bastien <[email protected]>: > >> Hi, >> >> Block data entrance ? >> > > Hello, > > We do not know how busy table is. There may be new data entered and data > moving application is already working on an executed query data which > doesn't include those new rows. > > Because of that possible data loose I would strong suggest one should stop > new data entrance while doing such operation on a production database. > > Regards, > Ertan > > > >> I have never tested a situation where data is entering a database/ table >> and I rename a single field , or column or table and even the Database >> itself >> >> Can you please guest or anticipate the respond of the server's or the >> application's error handling and/or exceptions ? >> >> Would there be ? >> >> regards >> >> >
