Subject Re: [firebird-support] Migrating from 1.56 to FB 3 - making good progress
Author Kevin Stanton
Cool. I will try the IB Expert Data Export feature first on the new/empty FB3 database.

If I have to recompile all objects, is there an “easy” way to do this?

Thanks!
Kevin





> On Oct 2, 2019, at 10:24 AM, 'Carlos H. Cantu' listas@... [firebird-support] <firebird-support@yahoogroups.com> wrote:
>
> KSKSRScfs> My question:
> KSKSRScfs> Now that my 1.56 metadata script works w/out error with
> KSKSRScfs> the 3.0 database, can I simply backup the 1.56 database and restore under FB 3?
>
> In theory, yes. But note that the BLR of existing objects (procedures,
> etc) are not recompiled when you do a restore, so, maybe you would
> like to recreate all the procedures, triggers, etc. after restoring
> the database to be sure that they are recompiled in FB 3.
>
> Vlad said to me that there are some benefits of recompiling the
> objects in FB 3: New engine could use new blr, also it will create
> "debug info" for sp\triggers - it allows to produce error messages
> with line numbers in call stack.
>
> []s
> Carlos
> https://www.firebirdnews.org/migration-guide-to-firebird-3/ <https://www.firebirdnews.org/migration-guide-to-firebird-3/>
>
> KSKSRScfs> Greetings!
>
> KSKSRScfs> I have been successfully created a script of the metadata
> KSKSRScfs> in the 1.56 database, ran the script against FB 3 (all using IB Expert).
>
> KSKSRScfs> Initial attempt only revealed about 20 or so errors. Not
> KSKSRScfs> too bad for a fairly complex 20-year old database.
>
> KSKSRScfs> I have fixed all the errors and can now run the script with no warnings or errors.
>
> KSKSRScfs> The trick is populating the 3.0 database. I know there
> KSKSRScfs> are data pump tools out there but they seem to be old?
>
> KSKSRScfs> My question:
> KSKSRScfs> Now that my 1.56 metadata script works w/out error with
> KSKSRScfs> the 3.0 database, can I simply backup the 1.56 database and restore under FB 3?
>
> KSKSRScfs> Thanks in advance!
>
> KSKSRScfs> Kevin
>
>
>



[Non-text portions of this message have been removed]