Discussion:
Progress message during dump and load database
(too old to reply)
Jesus M. Salvo Jr.
2006-05-22 06:49:45 UTC
Permalink
ASE 12.5.3 ESD#4

I do dump database with the 'with compression' clause. When I load the same
dump files, why is it that the number of KBs dumped is not the same as KBs
loaded ?

I am referring to the progress message that backup server logs, such as:

Backup Server: 4.58.1.1: Database motiondb: 56073792 kilobytes LOADed.
Backup Server: 4.58.1.1: Database motiondb: 56680010 kilobytes LOADed.

The number of KBs loaded seems to be a lot more than the number KBs dumped.
Eric McGrane
2006-05-22 14:33:11 UTC
Permalink
Post by Jesus M. Salvo Jr.
ASE 12.5.3 ESD#4
I do dump database with the 'with compression' clause. When I load the same
dump files, why is it that the number of KBs dumped is not the same as KBs
loaded ?
Backup Server: 4.58.1.1: Database motiondb: 56073792 kilobytes LOADed.
Backup Server: 4.58.1.1: Database motiondb: 56680010 kilobytes LOADed.
The number of KBs loaded seems to be a lot more than the number KBs dumped.
Jesus,

It is because the pages in the db that were not contained in the dump
need to be zeroed out. The number of kb loaded should be the size of
the db, give or take.

As an example. I dumped a db that is 1248 MB in size, 1000 MB data and
248 log. When I dumped it 335798 KB was dumped, when I loaded, 1278038
KB was loaded, the size of the db is 1277952 KB. Why is the size loaded
bigger than the db? I believe it is because some pages may be dumped
more than once but am not 100% sure.

E
Sybase
2006-05-22 16:09:06 UTC
Permalink
While loading the empty space will get allocated for future allocations.
Despite dump DB having lesser space, the entire db is initilised
Post by Jesus M. Salvo Jr.
ASE 12.5.3 ESD#4
I do dump database with the 'with compression' clause. When I load the same
dump files, why is it that the number of KBs dumped is not the same as KBs
loaded ?
Backup Server: 4.58.1.1: Database motiondb: 56073792 kilobytes LOADed.
Backup Server: 4.58.1.1: Database motiondb: 56680010 kilobytes LOADed.
The number of KBs loaded seems to be a lot more than the number KBs dumped.
Jesus M. Salvo Jr.
2006-05-23 02:01:58 UTC
Permalink
Post by Sybase
While loading the empty space will get allocated for future allocations.
Despite dump DB having lesser space, the entire db is initilised
Ahh ... that makes sense then.

Thanks.

Loading...