The FTDNA_ICW2 table stores FTDNA “In Common With” (ICW) relationships — pairs of your matches who also match each other. Each row records that, within one of your kits, two matches share DNA in common.
eKitKit is the kit whose shared-match list these relationships come from (your kit). eKitMatch1 and eKitMatch2 are the in-common pair — two of that kit’s matches who appear on each other’s shared-match lists.| Column | Type | Description |
|---|---|---|
| Id | int (PK) | Auto-incrementing primary key |
| eKitKit | string | The kit whose shared matches these are (your kit). Indexed. |
| eKitMatch1 | string | The first kit of the in-common pair. Indexed. |
| eKitMatch2 | string | The second kit of the in-common pair. Indexed. |
| created_date | string | Date the row was created (gather date, yyyy-MM-dd) |
| GF_Sync | string | Sync tracking flag |
During FTDNA ICW gathering, the client walks each of your matches and requests that match’s shared-match list. For your kit (eKitKit) and a given match, every other match that appears on its shared list is recorded as an in-common pair.
Each pair is written in both directions — one row with the original match as eKitMatch1 and the shared match as eKitMatch2, and a second row with the two swapped — so the relationship can be looked up from either side. Rows are de-duplicated on insert: a pair already present for the same (eKitKit, eKitMatch1, eKitMatch2) is not inserted again. Completing the shared-match list for a match also stamps icw_date on that match’s row in FTDNA_Matches2.
eKitKit, eKitMatch1, eKitMatch2) correspond to FTDNA_Matches2.eKit2 values (and eKitKit to eKit1).