>
> The application's purpose is to modify the structure of existing
> tables with data that were used for older version of some client
> program so that the database would be acceptable for the newer
> version of this program. The workaround is not acceptable due to huge
> amount of time required for copying the data from the old tables.
>
> Also we have found that in case of reconnecting to server after
> described error appears, next DDL commands are executed correctly
> (but then, after executing the same count of commands the begin to
> fail again). Maybe this variable is stored only during the connect
> session.
>
>
>

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.






Rob Martin
Software Engineer

phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com

Wild Software Ltd