SQL Server replication tables and procedures--and replication-related system tables and system stored procedures

Source: Internet
Author: User

Replicated tables in the primary database

Table name Description
MSreplication_options The table stores metadata that is used internally for replication. This table is stored in the master database.

Replicated tables in the msdb database

Table name Description
Msagentparameterlist The table contains replication agent parameter information that specifies the parameters that can be set for a given proxy type. The table is stored in the msdb database.
Msdbms The table contains a master list of all version database management systems (DBMS) that support heterogeneous database replication. The table is stored in the msdb database.
Msdbms_datatype In heterogeneous database replication, the Msdbms_datatype table stores a complete list of native data types in each supported database management system (DBMS) that is used as a Publisher or Subscriber. The table is stored in the msdb database.
Msdbms_datatype_mapping The table contains data type mappings that allow data types from the source database management system (DBMS) to one or more specific data types in the target DBMS. This table is stored in the msdb database and is used for heterogeneous database replication.
Msdbms_map The table contains the source data type information for the source and target DBMS pairs and a link to the default target data type information. The table is stored in the msdb database and is used for heterogeneous publishing.
Msreplmonthresholdmetrics The table defines the hops that are used to monitor replication. The table is stored in the msdb database.
Sysreplicationalerts Contains information about the conditions that caused the replication alert to fire. The table is stored in the msdb database.

Replication tables in the distribution database

Table name Description
MSagent_parameters The table contains the parameters associated with the proxy configuration file. The parameter name is the same as the name supported by the proxy. The table is stored in the msdb database.
MSagent_profiles The replication agent configuration file for each definition corresponds to a row in the MSagent_profiles table. The table is stored in the msdb database.
MSarticles Each item replicated by the publisher corresponds to a row in the MSarticles table. This table is stored in the distribution database.
Mscached_peer_lsns The table is used to track LSN values in the transaction log, which are used to determine the commands to be returned to a given subscriber in peer replication. This table is stored in the distribution database.
Msdistpublishers Each remote publisher supported by the local distributor corresponds to a row in the Msdistpublishers table. The table is stored in the msdb database.
Msdistribution_agents A row for each Distribution Agent running on the local distributor in the table. This table is stored in the distribution database.
MSdistribution_history The table contains the history rows for the Distribution Agent associated with the local distributor. This table is stored in the distribution database.
MSdistributiondbs A row for each distribution database defined on the local distributor in the table. The table is stored in the msdb database.
MSdistributor The table contains the properties of the Distributor. The table is stored in the msdb database.
MSlogreader_agents Each Log Reader Agent that runs on the local distributor corresponds to a row in the MSlogreader_agents table. This table is stored in the distribution database.
Mslogreader_history The table contains the history rows for the Log Reader Agent associated with the local distributor. This table is stored in the distribution database.
MSmerge_agents A row for each Merge Agent that runs at the Subscriber in the table. This table is stored in the distribution database.
MSmerge_history The table contains a detailed description of the history row, which includes the results of the previous Merge Agent job session. Each row of the proxy output corresponds to a row in the table. This table is used in the distribution database and in each subscription database. In the distribution database, the table contains the history of all merge publications and subscriptions that use the Distributor. In each subscription database, the table contains a history of the publications that subscribed to the subscriber alignment.
Msmerge_sessions The table contains the history rows, which have the results of the previous Merge Agent job session. Each time the Merge Agent is run, a new row is added to the table. This table is stored in the distribution database.
MSmerge_subscriptions Each subscription that is serviced by the Merge Agent at the Subscriber corresponds to a row in the MSmerge_subscriptions table. This table is stored in the distribution database.
MSpublication_access Each Microsoft SQL server login that has access to a specific publication or publisher has a row in the MSpublication_access table. This table is stored in the distribution database.
Mspublications Table, one row for each publication replicated by the publisher. This table is stored in the distribution database.
Mspublicationthresholds Tables are used to track replication performance hops for a publication, and each monitored threshold corresponds to a row in the table. This table is stored in the distribution database.
MSpublisher_databases each publisher that is serviced by a local distribution server / the publisher database is mspublisher_databases the table occupies a row. This table is stored in the distribution database.
MSreplication_objects Each object associated with replication in the Subscriber database corresponds to a row in the MSreplication_objects table. The table is stored in the subscription database.
MSreplication_subscriptions Table provides one-line replication information for each Distribution Agent that serves the local subscriber database. The table is stored in the subscription database.
MSrepl_commands The table contains the copy command line. The table is stored in the distribution database.
MSrepl_errors The table contains rows with extended Distribution Agent and Merge Agent failure information. This table is stored in the distribution database.
MSrepl_originators Each updatable subscriber that initiates a transaction corresponds to a row in the MSrepl_originators table. This table is stored in the distribution database.
MSrepl_transactions One row for each duplicate transaction in the table. This table is stored in the distribution database.
Msrepl_version In the Msrepl_version table, there is a row for the current version of the copy that is installed. This table is stored in the distribution database.
Mssnapshot_agents A row for each Snapshot Agent associated with the local distributor in the table. This table is stored in the distribution database.
MSsnapshot_history The table contains the history rows for the Snapshot Agent associated with the local distributor. The table is stored in the distribution database.
MSsubscriber_info Each pair of publishers/subscribers that are pushing subscriptions from the local distributor takes one row in the MSsubscriber_info table. This table is stored in the distribution database.
Mssubscriber_schedule The table contains the default merge and transaction synchronization schedules for each Publisher/Subscriber. This table is stored in the distribution database.
MSsubscriptions A row in the MSsubscriptions table for each published item in a subscription that is serviced by a local distributor. This table is stored in the distribution database.
MSsubscription_properties The table contains rows that run the parameter information required by the replication agent at the Subscriber. For pull subscriptions, the table is stored at the subscriber's subscription database, and for push subscriptions, the table is stored in the distribution database of the Distributor.
MStracer_history Table maintains a record of all tracer tokens that the Subscriber has received. This table is stored in the distribution database, and the replication process uses this table to monitor performance.
MStracer_tokens

The table maintains a record of the tracking token records that are inserted into the publication. This table is stored in the distribution database, and the replication process uses this table to monitor performance.

These tables in the distribution database can be used to replicate data from non-SQL Server Publishers .

For more information, see Non-SQL Server publishers.

Table name Description
Iharticles In the Iharticles system table, one row for each item copied from a non-SQL Server Publisher that uses the current distributor. This table is stored in the distribution database.
Ihcolumns Each published column occupies one row in the Ihcolumns system table. This table is used to define how a non-SQL Server Publisher's column data type is represented when it is published, and it actually maps data types between non-SQL Server database management systems (DBMS) and SQL Server. The table is stored in the distribution database.
Ihconstrainttypes
Each non-SQL Server constraint type that is supported by a non-SQL Server Publisher occupies one row in the Ihconstrainttypes system table. This table is stored in the distribution database.
Ihindextypes Table Non - SQL Server the Publisher supports every non- SQL Server the index type corresponds to one row. This table is stored in the distribution database.
Ihpublications Each non-SQL Server publication that uses the current distributor occupies one row in the Ihpublications system table. This table is stored in the distribution database.
Ihpublishercolumnconstraints The table maps the columns published by non-SQL Server ihpublishercolumns system tables to constraints in the ihpublisherconstraints system tables. This table is stored in the distribution database.
Ihpublishercolumnindexes The table maps the columns published by non-SQL Server ihpublishercolumns system tables to the indexes in the ihpublisherindexes system tables. This table is stored in the distribution database.
IHpublishercolumns
Table provides metadata that is stored at the publisher. Each column that is copied from a non-SQL Server Publisher using the current distributor is mapped to a row in that table. The data type information in IHpublishercolumns is specific to the non-SQL Server database management System (DBMS) from which data is published. This table is stored in the distribution database.
Ihpublisherconstraints For each constraint that is replicated from a non-SQL Server Publisher using the current distributor, the Ihpublisherconstraints system table contains a row accordingly. The table is stored in the distribution database.
IHpublisherindexes The table uses a row for each index that the current distributor replicates from a non-SQL Server Publisher. This table is stored in the distribution database.
Ihpublishers Table, a row for each non-SQL Server Publisher that uses the current distributor. This table is stored in the distribution database.
IHpublishertables system tables provide metadata that is stored at the publisher. Each source table published from a non-SQL Server Publisher using the current distributor corresponds to a row in this table. This table is stored in the distribution database.
Ihsubscriptions Each subscription published in a non-SQL Server Publisher that uses the current distributor is mapped to a row in the Ihsubscriptions system table. This table is stored in the distribution database.

SQL Server replication tables and procedures--and replication-related system tables and system stored procedures

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.