Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: The article order specified in the @processing_order parameter of sp_addmergearticle does not reflect the primary key-foreign key relationships between published tables. Article ‘%s’ references one or more articles that will be created after it is created. Change the processing_order property using sp_changemergearticle.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Merge table articles do not support different values for the @source_object and @destination_object parameters of sp_addmergearticle. Either do not specify a value for @destination_object, or specify the same value for both parameters.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Cannot enable the publication to support non-SQL Server subscriptions because the publication is enabled for updatable subscriptions. To support non-SQL Server subscriptions, drop the existing publication and create a new one with the properties allow_sync_tran and allow_queued_tran set to ‘false’.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Cannot change enabled for heterogeneous subscriptions property while there are subscriptions to the publication.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Cannot add article ‘%s’ with one or more dynamic functions in the subset_filterclause ‘%s’ to publication ‘%s’ because the publication could have active subscriptions. Set @force_reinit_subscription to 1 to add the article and reinitialize all active subscriptions.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Cannot change the value of validate_subscriber_info for publication ‘%s’ because the publication has active subscriptions. Set @force_reinit_subscription to 1 to change the value and reinitialize all active subscriptions.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Invalid value “%s” specified for the parameter @identityrangemangementoption. Valid values are “auto”, “manual”, or “none”.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: The property “%s” cannot be modified for publications that are enabled for non-SQL Server subscriptions.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Peer-to-peer publications do not support %s. Change the value for parameter ‘%s’.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Cannot modify property ‘%s’. The publication is used in a peer-to-peer topology, which does not allow this property to be modified after the publication is created.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: An article already exists for table “%s” with a different value for the @delete_tracking property. The value must be the same for all publications in which the table is published. Use the stored procedures sp_helpmergearticle and sp_changemergearticle to view and modify the property in the other article(s).

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Publications enabled for heterogeneous subscriptions do not support %s. Please change the ‘%s’ parameter value.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Cannot enable data definition language (DDL) replication (a value of “true” for the @replicate_ddl parameter) for publication “%s”. This is because the compatibility level of the publication is lower than 90RTM. For new publications, in the stored procedure sp_addmergepublication, set the @publication_compatibility_level parameter to 90RTM; for existing publications, use sp_changemergepublication.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Publication “%s” “%s”. Therefore the compatibility level of the publication cannot be set to lower than %d. To set the compatibility level lower, disable the feature and then call the stored procedure sp_changemergepublication to lower the compatibility level.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Required metadata for publication ‘%s’ could not be found in the sysmergeschemachange system table. Run the Snapshot Agent again.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: Cannot have a dynamic snapshot job with both dynamic_filter_login and dynamic_filter_hostname being NULL.

Microsoft SQL Server database ranks third in the r… Continue Reading Microsoft SQL Server: The partitioned snapshot process cannot complete. Cannot retrieve the maximum timestamp information from the MSsnapshot_history table in the distribution database. Ensure that a standard snapshot is up-to-date and available.