Article Issues
You may receive a message stating that you have an article issue after you select the articles that you want to publish. This messages states conditions that have been found and actions, if any, performed by Microsoft® SQL Server™ 2000.
| Article Issue | Details |
|---|---|
| uniqueidentifier columns will be added to tables. | SQL Server requires that all merge articles contain a uniqueidentifier column with a unique index and the ROWGUIDCOL property. SQL Server will add a uniqueidentifier column to published tables that do not have one when the first snapshot is generated. For more information, see Merge Replication. |
| timestamp columns will be added to tables. (for Publishers running SQL Server 7.0). | SQL Server requires that all articles in a publication allowing updatable subscriptions contain a timestamp column used for tracking changes to the replicated data. SQL Server will add a timestamp column to those published tables that do not have one. For more information, see Immediate Updating. |
| Uniqueidentifier columns will be added to tables. | SQL Server requires that all articles in a publication allowing updatable subscriptions contain a uniqueidentifier column named 'MSrepl_tran_version' used for tracking changes to the replicated data. SQL Server will add such a column to published tables that do not have one. For more information, see Updatable Subscriptions. |
| IDENTITY columns require the NOT FOR REPLICATION option. | SQL Server requires that all IDENTITY columns use the NOT FOR REPLICATION option. If a published IDENTITY column does not use this option, INSERT commands may not replicate properly. For more information, see Using NOT FOR REPLICATION. |
| IDENTITY property not transferred to Subscribers. | Because this publication does not allow updatable subscriptions, when IDENTITY columns are transferred to the Subscriber, the IDENTITY property will not be transferred. (For example, a column defined as INT IDENTITY at the Publisher will be defined as INT at the Subscriber.) For more information, see Using IDENTITY Values with Replication. |
| Tables referenced by views are required. | SQL Server requires that all tables referenced by published views and indexed views be available at the Subscriber. If the referenced tables are not published as articles in this publication, they must be created at the Subscriber manually. For more information, see Publishing Data and Database Objects. |
| Objects referenced by stored procedures are required. | SQL Server requires that all objects referenced by published stored procedures, such as tables and user-defined functions, be available at the Subscriber. If the referenced objects are not published as articles in this publication, they must be created at the Subscriber manually. For more information, see Publishing Data and Database Objects. |
| Indexed view articles are supported only in SQL Server 2000, Enterprise Edition. | Indexed views are supported only in Microsoft SQL Server 2000, Enterprise Edition. You have published one or more indexed view articles that create an indexed view at the Subscriber. For Subscribers that are servers running Microsoft SQL Server, only those running SQL Server 2000, Enterprise Edition will be able to subscribe to this publication. For more information, see Publishing Data and Database Objects. |
| Heterogeneous Subscribers may not support BIGINT IDENTITY columns. | You have enabled identity range management for one or more published tables that contain a BIGINT IDENTITY column. Some heterogeneous Subscribers may not support the IDENTITY property or automatic IDENTITY value management for this column. Such Subscribers may allow IDENTITY column values that could result in duplicate key violations or other synchronization conflicts. For more information, see Managing Identity Values. |