Appendix B: Changes to Commands, System Procedures, and Databases

Other changes to system procedures

This section describes system procedures that exhibit behavior changes when Adaptive Server is configured for failover. After Adaptive Server is configured as a companion server:

System procedures exhibit no changes 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 the failback mode.
The “Normal companion mode,” column of Table B-2 and Table B-3 describes the behavioral changes for system procedures issued from an asymmetric primary, asymmetric secondary, or symmetric companion.
The “Failover mode,” column of Table B-2 and Table B-3 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.
You cannot these system procedures during asymmetric secondary suspended mode or symmetric suspended mode.
An X indicates that the system procedure does not run in the listed mode.

**Table B-2: Changes in system procedures that alter server-wide attributes**
System procedure	Normal companion mode	Asymmetric primary suspended mode	Failover mode
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.

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.

**Table B-3: Changes that alter database-wide attributes when they are run in master**
System procedure	Normal companion mode	Asymmetric primary suspended mode	Failover mode	Notes
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 on this system procedure.

sp_changedbowner and sp_renamedb run during failover mode; additionally, they exhibit these 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, 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.

dbcc options for high availability systems

View this book as PDF