Adaptive Server 15.7 ESD #2 includes enhancements to the dump and load commands:
The dump configuration command allows you to back up the Adaptive Server configuration file, the dump history file, and the cluster configuration file. See the Reference Manual:Commands.
Adaptive Server 15.7 ESD #2 introduces dump configurations that define the options to create a database dump. Backup Server then uses the configuration to perform a database dump. You can use:
The dump configuration to create, modify, or list dump configurations, then use dump database or dump transaction with the dump configurations to perform dumps. See the Reference Manual:Commands. See the Reference Manual:Procedures for information about sp_config_dump.
The enforce dump configuration configuration parameter to enable dump operations with dump configurations. See “Configuration parameters”.
The configuration group “dump configuration” that represents user-created dump configurations. See “Using dump configurations”.
Dump history – Adaptive Server 15.7 ESD #2 allows you to:
Preserve the history of dump database and dump transaction commands in a dump history file that Adaptive Server can later use to restore databases up to a specified point in time. See “Dump history file”.
Read the dump history file and regenerate the load sequence of SQL statements necessary to restore the database. Use:
load database with listonly=load_sql until_time = datetime
For details on extensions to load database, see the Reference Manual:Commands.
Use the sp_dump_history system procedure to purge dump history records.
For details on sp_dump_history, see the Reference Manual:Procedures.
Use the enable dump history configuration parameter to disable default updates to the dump history file at the end of every dump operation.
Use the dump history filename configuration parameter to specify the name of the dump history file.
The dump with listonly command has been enhanced in Adaptive Server 15.7 ESD #2 to provide two options. You can:
Use the create_sql option to list the sequence of disk init, sp_cacheconfig, create database, and alter database commands that are needed to create a target database with the same layout as the source database.
Use the load_sql option, which uses the dump history file to generate the list of load database and load transaction commands that are needed to repopulate the database to a specified point in time.
For details on extensions to load database and load transaction, see the Reference Manual:Commands.
For details on the enhanced dump header, see “Enhancements to dump header”.
