Forces the SAP ASE server to recognize changes made by alter database. Run this procedure only when instructed to do so by an SAP ASE message.


sp_dbremap dbname




There are additional considerations when using sp_dbremap:
  • If an alter database statement issued on a database that is in the process of being dumped is interrupted, the SAP ASE server prints a message instructing the user to execute sp_dbremap.

  • Any changes to sysusages during a database or transaction dump are not copied into active memory until the dump completes, to ensure that database mapping does not change during the dump. Running alter database makes changes to system tables on the disk immediately. In-memory allocations cannot be changed until a dump completes. This is why alter database pauses.

    When you execute sp_dbremap, it must wait until the dump process completes.

  • If you are instructed to run sp_dbremap, but do not do it, the space you have allocated with alter database does not become available to the SAP ASE server until the next restart.

See also:
  • alter database, dump database, dump transaction in Reference Manual: Commands


The permission checks for sp_dbremap differ based on your granular permissions settings.


With granular permissions enabled, you must be the database owner or a user with own database privilege on the database.


With granular permissions disabled, you must be the database owner or a user with sa_role.


Values in event and extrainfo columns from the sysaudits table are:



Audit option


Command or access audited

Execution of a procedure

Information in extrainfo
  • Roles – Current active roles

  • Keywords or options – NULL

  • Previous value – NULL

  • Current value – NULL

  • Other information – All input parameters

  • Proxy information – Original login name, if set proxy in effect