MSA lets you replicate DDL to nonstandby databases. See Chapter 3, “Managing Warm Standby Applications” in the Replication Server Administration Guide Volume 2 for a list of DDL commands supported for replication.
To replicate DDL and system procedures, you must:
Mark the primary database using sp_reptostandby.
Set the RepAgent parameter send warm standby xacts to true—even if there is no standby database.
Create a database subscription.
Make sure that both the primary and replicate data servers are the same version of Adaptive Server.
In addition, the following constraints apply:
When replicating system procedures, and the primary and replicate databases have different names – filter out the sp_config_rep_agent and the sp_add_user system procedures in the database replication definition as they use database names as parameters. For example:
create database replication definition myrepdef with primary at PDS.pdb not replicate system procedures in (sp_config_rep_agent, sp_add_user)
When replicating DDL – the primary and replicate databases must have the same login names and passwords; the DSI uses the original server login name and password to log in to the replicate database.
When replicating DDL contained in user-defined transactions – make sure that the Adaptive Server database option ddl in tran is set to true. Otherwise, the DSI will shut down when replicating DDL.
In a heterogeneous environment, non-Sybase data servers can replicate DDL if the Replication Agent can capture and send DDL commands in Transact-SQL or ANSI SQL (preferred).
