Save transactions to another location before dispatch

[LMeden]

Hi,

Is it possible to save transactions on another location then the local client, before performing a dispatch?

/Lars

[LMeden]

Thanks for your reply.

[jhorber · Accepted solution]

Hello Lars

It is not possible to change the physical location of existing transactions by changing a parameter/option.

• With GBMS storage (except with local cache), transactions are files located in a subfolder of the MEGA environment
• With RDBMS storage, transactions are records in tables located in the database server

Notes:

With GBMS storage, you can consider to move the environment folder and change the reference.

Of course

• The MEGA environment should not be used during the transfer.
• End users need to have appropriate file permissions on the target folder.

In any case, you can save the content of a transaction to a command file (transation logfile) by exporting it (menu Tools > Manage > Export Updates Logfile)