Learn how Adaptive Server determines the database in which a replicated stored procedure execution is logged.
If the user does not explicitly begin a transaction, Adaptive Server begins one in the user’s current database before the stored procedure execution.
If the user begins the transaction in one database, and then executes a replicated stored procedure in another database, the execution is still ogged in the database where the user began the transaction.
If the execution of a table-style replicated stored procedure (marked for replication by using either sp_setreplicateproc_name, 'true' or sp_setrepprocproc_name, 'table') is logged in one database and changes replicated tables in another database, the table’s changes and the procedure execution are logged in different databases. Therefore, the effects of the stored procedure execution can be replicated twice: the first time, the stored procedure execution itself is replicated; the second time, table changes that have been logged in the other database are replicated.
Replicated Adaptive Server stored procedures cannot contain parameters with the text, unitext, or image datatypes.
See the Adaptive Server Reference Manual
If a single transaction that invokes one or more request stored procedures is a mixed-mode transaction that also executes applied stored procedures or contains data modification language, Replication Server processes the request stored procedures after all the other operations.
All request operations are processed together in a single separate transaction. This may occur when a single Replication Server manages both primary and replicate data.