Block non-logged operations

You should consider setting the database configuration parameters blocknonlogged for high availability disaster recovery (HADR) databases.

Using the blocknonlogged database configuration parameter

Recommendation: For HADR databases, set the blocknonlogged database configuration parameter to YES to prevent operations that are not fully logged. Such operations include:

CREATE TABLE and ALTER TABLE statement with NOT LOGGED INITIALLY option
CREATE TABLE and ALTER TABLE statement with NOT LOGGED parameter for a LOB column
LOAD command with NONRECOVERABLE option
LOAD command with COPY NO option

These non-logged operations will cause the table on standby to not be maintained. When the standby becomes a new primary after failover, access to the table will not be possible, or in the case of the NOT LOGGED LOB column, the data will all be binary 0. This can be a significant impact to applications. Therefore, it is recommended to prevent these operations by configuring the blocknonlogged database configuration parameter.