| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | f1_keywords | helpviewer_keywords | dev_langs | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
MSmerge_genhistory (Transact-SQL) |
MSmerge_genhistory (Transact-SQL) |
VanMSFT |
vanto |
03/04/2017 |
sql |
replication |
reference |
|
|
|
[!INCLUDE SQL Server]
The MSmerge_genhistory table contains one row for each generation that a Subscriber knows about (within the retention period). It is used to avoid sending common generations during exchanges and to resynchronize Subscribers that are restored from backups. This table is stored in the publication and subscription databases.
| Column name | Data type | Description |
|---|---|---|
| guidsrc | uniqueidentifier | The global identifier of the changes identified by generation at the Subscriber. |
| pubid | uniqueidentifier | The publication identifier. |
| generation | bigint | The generation value. |
| art_nick | int | The nickname for the article. |
| nicknames | varbinary(1001) | A list of nicknames of other Subscribers that are known to already have this generation. It is used to avoid sending a generation to a Subscriber that has already seen those changes. Nicknames in the nicknames list are maintained in sorted order to make searches more efficient. If there are more nicknames than can fit in this field, they will not benefit from this optimization. |
| coldate | datetime | Date when current generation is added to the table. |
| genstatus | tinyint | The status of the generation as follows: 0 = Open. 1 = Closed. 2 = Closed and originated at another Subscriber. |
| changecount | int | The number of changes reflected in a given generation |
Replication Tables (Transact-SQL)
Replication Views (Transact-SQL)