When a data server begins rejecting transactions because of a temporary failure, such as lack of space in a database or log file, you can suspend the database connection until the error is corrected.
If the database connection is not suspended, Replication Server writes the transactions into the exceptions log for the database. Since these transactions must then be resolved manually, you can save time by shutting down the connection until the error condition is corrected.
While a database connection is suspended, Replication Server stores transactions in a stable queue. When the connection is resumed, the stored transactions are sent to the data server.
To stop the flow of transactions from a Replication Server to a database, use the suspend connection command:
suspend connection to data_server.database
The command requires sa permission and must be entered at the Replication Server that manages the database.
