On 2/14/2011 4:10 AM, karolbieniaszewski wrote:

>

>
> I hope that indeed the problem was fixed.
> I need to check yourself and see what happens ..
>

First, transaction identifiers are 32 bits on all platforms. The
transaction is stored in every record version, so doubling it would
have a significant effect on the number of back versions that can
be stored on a page. And, the space would be wasted for the vast
majority of databases.

Second, the bug fix handled the case where the database ran out
of transaction identifiers and backup could not run because it
couldn't get a transaction identifier. It did not eliminate the
risk of overrun.

You might look at developing some way to track changes that
happen during a backup/restore and apply them after the restore
completes.


Good luck,

Ann