The sybsystemprocs database stores only system procedures. Restore this database by running the installmaster script, unless you make changes to the database.
If you change permissions on some system procedures, or create your own system procedures in sybsystemprocs, your two recovery choices are:
Run installmaster, then reenter all of your changes by re-creating your procedures or by re-executing the grant and revoke commands.
Back up sybsystemprocs each time you make a change to it.
Both of these recovery options are described in Chapter 29, “Restoring the System Databases.”
Like other system databases, sybsystemprocs stores its transaction log on the same device as the data. You must always use dump database to back up sybsystemprocs. By default, the trunc log on chkpt option is set to true (on) in sybsystemprocs, so you should not need to truncate the transaction log. If you change this database option, be sure to truncate the log when you dump the database.
If you are running on a UNIX system or PC, and you have only one Adaptive Server that can communicate with your Backup Server, be sure that the entire dump of sybsystemprocs fits on a single dump device. Signaling volume changes requires sp_volchanged, and you cannot use this procedure on a server while sybsystemprocs is in the process of recovery.
