I think I am right in saying that the Update files created by EDB when a user called "Save Updates" are not compressed. As a result these update files can be extremely large, particularly where a user has run a fairly wide-ranging "update" statement.

In replication it is common for these files to be passed around WAN's sometimes with limited bandwidth.

It is great to be able to Query the content of an Update file to find its content, but it would also be useful to have the file-size reduced by compressing them when created to speed up the file copy process.

Adam,

<< I think I am right in saying that the Update files created by EDB when a
user called "Save Updates" are not compressed. As a result these update
files can be extremely large, particularly where a user has run a fairly
wide-ranging "update" statement. >>

Nope, they're compressed (default level of 6), and you can change it with
the COMPRESSION clause:

http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=SAVE_UPDATES

Tim Young
Elevate Software
www.elevatesoft.com

Tim

><< I think I am right in saying that the Update files created by EDB when a
>user called "Save Updates" are not compressed. As a result these update
>files can be extremely large, particularly where a user has run a fairly
>wide-ranging "update" statement. >>
>
>Nope, they're compressed (default level of 6), and you can change it with
>the COMPRESSION clause:

Not used this so a supplementary question - are they encrypted as the tables are and if so what impact does that have on compression?

Roy

>>Nope, they're compressed (default level of 6), and you can change it with
>>the COMPRESSION clause:

>>http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=SAVE_UPDATES


... D'Oh.

Roy,

<< Not used this so a supplementary question - are they encrypted as the
tables are and if so what impact does that have on compression? >>

No, they are not encrypted.

Tim Young
Elevate Software
www.elevatesoft.com