Scheduling Dumps

Considerations for scheduling dumps.

  • SAP ASE database dumps are dynamic—they can take place while the database is active. However, they may slow the system down slightly, so you may want to run dump database when the database is not being heavily updated.

  • Back up the master database regularly and frequently. In addition to your regular backups, dump master after each create database, alter database, and disk init command is issued.

  • Back up the model database each time you make a change to the database.

  • Use dump database immediately after creating a database, to make a copy of the entire database. You cannot run dump transaction on a new database until you have run dump database.

  • Each time you add or remove a cross-database constraint or drop a table that contains a cross-database constraint, dump both of the affected databases.

    Warning!   Loading earlier dumps of these databases can cause database corruption.
  • Develop a regular schedule for backing up user databases and their transaction logs.

  • Use thresholds to automate backup procedures. To take advantage of SAP ASE last-chance threshold, create user databases with log segments on a device that is separate from data segments. For more information about thresholds, see the System Administration Guide.