> Hi
>
> I don't really understand what your application is trying to do.

It

> sounds like a conversion / upgrade tool. If so isn't this just a

one

> off process? If so you could do just do x amount of changes,

backup +

> restore and do the rest of the changes. This is slow but if it is

only

> a one off why not.
>
> Our application changes our database structure on each service pack
> release we do the following..
>
> a) Rename DB
> b) Create a new empty DB based on the new DB structure
> c) Pump Data from old DB to new DB
>
> This is not fast but it means we never have to bother with 'Alter'

table

> statements and if someone misses 1 or 2 service packs the proceses

can

> still work fine.
>

Hello!

Thank you for your answer!

Yes, our application is a conversion tool and it is fully automated
(so that the users may not know how to create backups for FB
databases). Also it is used to convert the databases with huge amount
of data; using DDL commands and UPDATE queries all the process of
conversion may last about 7-8 hours (though the conversion is partial
due to described error) and if we'd used your solution all the
process may last about a week or more and that is not acceptable.

The workaround with reconnection is better than that but maybe there
is something better?