When you create a database replication definition at the primary database, you must also create a database subscription at each subscribing database. You can use the no materialization method or the bulk materialization method. If you create a database subscription, you cannot use a where clause to set the criteria for subscribed data; all data is subscribed.
If you need to set criteria for particular tables or functions, you can add table or function subscriptions. See “Using database, table, and function subscriptions concurrently” for more information.
When there is a database subscription, the DSI for that connection is always treated as if for regular replication. That is, the dsi_replication parameter is off, and the dsi_keep_triggers parameter is on.
When there is a database subscription—and table and function replication definitions—but there are no table or function subscriptions:
If the table and function replication definitions contain the send standby clause, the database subscription honors the table or function replication definition.
If the table and function replication definitions do not contain the send standby clause, all columns and parameters are replicated and the data is converted to the declared column and parameter datatypes.
