Hi
Is there a negative effect on too many levels?
(Slowdown or database storage overhead?)
No negative effect.
The database does track the ID of the last backup at each level, so you would
have 2 or 3 more entries that the typical usage, but
the details are notional in size.
But as far
But as far as I understand, the database has to track which page changes
since which backup.
Correct, but that information is actually stored as a version number in the
header of each data page. When page data changes the version number is
changed.
The nbackup database structure only
Hi
Correct, but that information is actually stored as a version number in the
header of each data page. When page data changes
the version number is changed.
The nbackup database structure only stores the version number for the
backup level.
From a quick search, I suspect that will be
I have a legacy client that was running fine on XP with FB 1.5 but we've
recently switched the PC out for a Win7 Pro 64 bit system.
In order to get the client running on the Win7 system I installed FB 2.5 on it
and used gbak on the new system to restore the database file as a 2.5 version
One other bit...
I didn't use the -TRANSPORTABLE switch when I created the backup file on the
1.5 system Could this have something to do with the error ?
From a quick search, I suspect that will be the pag_scn 4 byte value.
I don't recall exactly, if you want to pursue this you should ask on the Devel
list for confirmation.
That would mean that I could relatively easily write my own sync code that
could also read all those values and decide
I have a legacy client that was running fine on XP with FB 1.5 but we've
recently switched the PC out for a Win7 Pro 64 bit system.
In order to get the client running on the Win7 system I installed FB 2.5 on it
and used gbak on the new system to restore the database file as a 2.5
version
One thing, that corresponds to Seans ideas: Formely you could used mixed
alias and table name in field list. Now, you've to be strict: Assign
alias and use alias (or no qualifier) or do not assign alias.
I.e.:
select t.C from tab t -- works
select tab.C from tab -- works
select C from tab
