Replication supports the publishing of partitioned tables and indexes. The level of support depends on the type of replication that is used, and the options that you specify for the publication and the articles associated with partitioned tables. For more information, see Replicating Partitioned Tables and Indexes.

• The maximum number of articles and columns that can be published differs by publication type. For more information, see the "Replication Objects" section of Maximum Capacity Specifications for SQL Server.
  
• Stored procedures, views, triggers, and user-defined functions that are defined as WITH ENCRYPTION cannot be published as part of SQL Server replication.
  
• XML schema collections can be replicated but changes are not replicated after the initial snapshot.
  
• Tables published for transactional replication must have a primary key. If a table is in a transactional replication publication, you cannot disable any indexes that are associated with primary key columns. These indexes are required by replication. To disable an index, you must first drop the table from the publication.
  
• Bound defaults created with sp_bindefault (Transact-SQL) are not replicated (bound defaults are deprecated in favor of defaults created with the DEFAULT keyword of ALTER TABLE or CREATE TABLE).
  

Replication has the following default behavior in the New Publication Wizard with respect to schemas and object ownership:

• For articles in merge publications with a compatibility level of 90 or higher, snapshot publications, and transactional publications: by default, the object owner at the Subscriber is the same as the owner of the corresponding object at the Publisher. If the schemas that own objects do not exist at the Subscriber, they are created automatically.
  
• For articles in merge publications with a compatibility level lower than 90: by default, the owner is left blank and is specified as dbo during the creation of the object on the Subscriber.
  
• For articles in Oracle publications: by default, the owner is specified as dbo.
  
• For articles in publications that use character mode snapshots (which are used for non-SQL Server Subscribers and SQL Server Compact 3.5 SP1 Subscribers): by default, the owner is left blank. The owner defaults to the owner associated with the account used by the Distribution Agent or Merge Agent to connect to the Subscriber.
  

The object owner can be changed through the Article Properties - <Article> dialog box and through the following stored procedures: sp_addarticle, sp_addmergearticle, sp_changearticle, and sp_changemergearticle. For more information, see How to: View and Modify Publication and Article Properties (SQL Server Management Studio), How to: Define an Article (Replication Transact-SQL Programming), and How to: View and Modify Article Properties (Replication Transact-SQL Programming).

• If you are publishing to a Subscriber running a previous version of SQL Server, you are limited to the functionality of that version, both in terms of replication-specific functionality and the functionality of the product as a whole. For example, you will not be able to publish user-defined data types or CLR functions to Subscribers running SQL Server 2000.
  
• Merge publications use a compatibility level, which determines what features can be used in a publication and allows you to support Subscribers running previous versions of SQL Server.
  

For more information, see Using Multiple Versions of SQL Server in a Replication Topology.

Replication supports publishing articles in multiple publications (including republishing data) with the following restrictions:

• If an article is published in a transactional publication and a merge publication, ensure that the @published_in_tran_pub property is set to TRUE for the merge article. For more information about setting properties, see How to: View and Modify Publication and Article Properties (SQL Server Management Studio) and How to: View and Modify Article Properties (Replication Transact-SQL Programming).
  You should also set the @published_in_tran_pub property if an article is part of a transactional subscription and is included in a merge publication. If this is the case, be aware that by default transactional replication expects tables at the Subscriber to be treated as read-only; if merge replication makes data changes to a table in a transactional subscription, non-convergence of data can occur. To avoid this possibility, we recommend that any such table be specified as download-only in the merge publication. This prevents a merge Subscriber from uploading data changes to the table. For more information, see Optimizing Merge Replication Performance with Download-Only Articles.
  
• An article cannot be published in both a merge publication and a transactional publication with queued updating subscriptions.
  
• Articles included in transactional publications that support updating subscriptions cannot be republished.
  
• If an article is published in more than one transactional publication that supports queued updating subscriptions, the following properties must have the same value for the article across all publications:
  

  Property	Parameter in sp_addarticle
  Identity range management	@auto_identity_range (deprecated) and @identityrangemangementoption
  Publisher identity range	@pub_identity_range
  Identity range	@identity_range
  Identity range threshold	@threshold

  For more information about these parameters, see sp_addarticle (Transact-SQL).
  
• If an article is published in more than one merge publication, the following properties must have the same value for the article across all publications:
  

  Property	Parameter in sp_addmergearticle
  Column tracking	@column_tracking
  Schema options	@schema_option
  Column filtering	@vertical_partition
  Subscriber upload options	@subscriber_upload_options
  Conditional delete tracking	@delete_tracking
  Error compensation	@compensate_for_errors
  Identity range management	@auto_identity_range (deprecated) and @identityrangemangementoption
  Publisher identity range	@pub_identity_range
  Identity range	@identity_range
  Identity range threshold	@threshold
  Partition options	@partition_options
  Blob column streaming	@stream_blob_columns
  Filter type	@filter_type (parameter in sp_addmergefilter)

  For more information about these parameters, see sp_addmergearticle (Transact-SQL) and sp_addmergefilter (Transact-SQL).
  
• Transactional replication and unfiltered merge replication support publishing a table in multiple publications and then subscribing within a single table in the subscription database (commonly referred to as a roll up scenario). Roll up is often used for aggregating subsets of data from multiple locations in one table at a central Subscriber. Filtered merge publications do not support the central Subscriber scenario. For merge replication, roll up is typically implemented through a single publication with parameterized row filters. For more information, see Parameterized Row Filters.