This section describes the system procedures whose behavior changes when Adaptive Server is configured for Failover. After Adaptive Server is configured as a companion server:
System procedures have no change to their default functionality when they are run in single-server mode.
You cannot run any of the system procedures listed in Table B-2 or Table B-3 during failback mode.
The first column of Table B-2 and Table B-3 “Normal Companion Mode,” describes the behavioral changes for system procedures issued from an asymmetric primary, asymmetric secondary, or symmetric companion.
The last column of Table B-2 Table B-3 “Failover Mode,” describes the behavioral changes for system procedures issued during either asymmetric secondary failover or symmetric failover.
Table B-2 lists the system procedures that change server-wide attributes (for example, the default language or the resource limit):
During normal companion mode, all the system procedures listed in Table B-2 must be run from master.
These system procedures cannot be run during asymmetric secondary suspended mode or symmetric suspended mode.
An X indicates that the system procedure does not run in the listed mode.
System procedure |
Normal Companion Mode |
Asymmetric Primary Suspended Mode |
Failover Mode |
|---|---|---|---|
sp_add_resource_limit |
|||
sp_add_time_range |
|||
sp_addexternlogin |
|||
sp_addlanguage |
|||
sp_addlogin |
|||
sp_addremotelogin |
|||
sp_addserver |
|||
sp_defaultdb |
|||
sp_defaultlanguage |
|||
sp_drop_resource _limit |
You must manually run this system procedure on the remote server as well to synchronize the companions |
X |
X |
sp_drop_time_range |
X |
X |
|
sp_dropexternlogin |
X |
X |
|
sp_droplanguage |
X |
X |
|
sp_droplogin |
X |
X |
|
sp_dropremotelogin |
X |
X |
|
sp_dropserver |
X |
X |
|
sp_locklogin |
|||
sp_modify_resource _limit |
You must manually run this system procedure on the remote server as well to synchronize the companions |
||
sp_modify_time_range |
|||
sp_password |
|||
sp_remotelogin |
|||
sp_remoteoption |
|||
sp_serveroption |
|||
sp_setlangalias |
Table B-3 lists the system procedures that change the attributes of the database in which they are run (such as adding a user, alias, or group to the current database). You cannot run these system procedures from master during either secondary suspended or symmetric suspended mode. An X indicates that you cannot run the system procedure in the listed mode.
System procedure |
Normal Companion Mode |
Asymmetric Primary Suspended Mode |
Failover Mode |
Notes |
|---|---|---|---|---|
sp_addalias |
||||
sp_addgroup |
||||
sp_addtype |
||||
sp_adduser |
||||
sp_changedbowner |
X |
See below for additional restrictions for this system procedure. |
||
sp_changegroup |
You must manually run this system procedure on the remote server as well to synchronize the companions |
|||
sp_dropalias |
X |
X |
||
sp_dropgroup |
X |
X |
||
sp_droptype |
X |
X |
||
sp_dropuser |
X |
X |
||
sp_renamedb |
X |
See below for additional restrictions for this system procedure. |
sp_changedbowner and sp_renamedb cannot run during failover mode, and have the following additional behavior changes:
sp_changedbowner – After you run this procedure on local companion, you must manually run it on the remote server as well to synchronize the companions if the following are true:
You are not running this command in master.
The companion is in suspended or normal companion mode
The companion was configured using the with_proxydb option.
sp_renamedb – You must first run this system procedure in the primary database and then run it in the proxy database on the remote server, if the following are true:
You do not run this command in master
The companion is in suspended or normal companion mode
The companion is configured using the with_proxydb option
