A replication definition that you create for a primary database applies to all primary connections, default and alternate, between the Replication Server that controls the replication definition and the primary database. Therefore, you must drop all replication definitions for the primary database before you drop the last primary connection to the primary database.
With system version 1570, you can create replication definitions and publications only against a database. The name you specify for the with primary at clause of the create replication definition command must be the primary database name.
create subscription sub_name for {table_repdef | func_repdef | publication pub | database replication definition db_repdef} with primary at data_server.database with replicate at data_server.database [where {column_name | @param_name} {< | > | >= | <= | = | &} value [and {column_name | @param_name} {< | > | >= | <= | = | &} value]...] [without holdlock | incrementally | without materialization] [subscribe to truncate table] [for new articles]
When you upgrade from a Replication Server version that does not support alternate connections, all subscriptions remain defined against the default primary connection and default replicate connection in the upgraded Replication Server.
create subscription sub_conn2 for repdef_conn2 with primary at LON_DS.pdb_conn2 with replicate at NY_DS.rdb without materialization go
create subscription sub_conn2 for repdef_conn2 with replicate at NY_DS.rdb_conn2 without materialization go