Known Issues for Replication Server Unsupported Operations

Learn about the known issues when using unsupported operations.

These Adaptive Server operations may cause incorrect replication:

Disabling the secondary truncation point with dbcc settrunc and then truncating the log can cause lost transactions.
Replication Server does not support nested transactions within replicated stored procedures.
When you enable replication for a stored procedure using sp_setrepproc or sp_setreplicate, Adaptive Server always runs the stored procedure within a transaction. If you have not explicitly run the replicated stored procedure within a transaction, Adaptive Server places an implicit begin transaction command at the start of the procedure.

If the replicated stored procedure contains nested transaction commands such as begin transaction, commit transaction, or rollback transaction, you might get errors when you run the procedure. For example, a rollback transaction command rolls back to the start of the stored procedure, rather than to the nested begin transaction command, which was the intended rollback point.
Data that is inserted into a primary table using an unlogged bulk copy operation is not replicated.
To use the atomic method of subscription materialization:
- The user who enters the create subscription command or the database owner must own the primary table. Alternatively, you must use user-defined function strings for select operations at the primary database.
- If the database owner or maintenance user does not own the replicate table, use user-defined function strings for select operations at the replicate database. If the owner of the replicate table is different from the owner of the primary table, create a unique function string by using a distinct function-string class.