Help › Database Reference

Database Reference

This section provides detailed documentation for each database table in the DNAGedcom Client. It covers column definitions, data sources, how fields are populated during gathering, and data preservation rules.

This is a technical reference for developers and advanced users. For general database information, see Database & Data Management.

A* Tables

TableDescription
Ancestry_matchGroupsPrimary match table. DNA match data, relationship predictions, shared cM, parent side, metadata.
Ancestry_MatchProfilePer-match profile data — match name, managing tester name, photo, and gender — keyed on matchGuid. Names moved here from Ancestry_matchGroups in the 2026-04-30 A* update.
Ancestry_matchDetailSupplemental per-match detail: shared-segment count, member-since year, and administrator UCDM id.
Ancestry_RelationshipPredictionsDetailed relationship predictions with ranked probabilities per match.
Ancestry_ICWIn Common With (shared match) relationships.
Ancestry_matchTreesFamily tree individuals linked to matches.
Ancestry_TreeDataTree metadata (tree ID, size, privacy status).
AncestryAncestorCoupleCommon ancestor couples shared between matches.
Ancestry_SharedBirthLocationsShared ancestral birth locations between the test and a match, with sample/match person counts.
Ancestry_SharedJourneysShared A* migration “journeys” between the test and a match.
Ancestry_MatchEthnicityRegionPer-match ethnicity estimate — region key and percentage for each match.
Ancestry_EthnicityRegionEthnicity region lookup: region key → display name and parent (macro) region.
Ancestry_EthnicityLegacy ethnicity code/value lookup.
Ancestry_LocationsBirth and death locations from match trees.
Ancestry_ProfilesDNA test profiles and kit information.
Ancestry_KitStored A* account/kit login credentials (internal).
As of the 2026-04-30 A* update, match and administrator names, photos, and gender live in Ancestry_MatchProfile (joined to Ancestry_matchGroups on matchGuid) rather than on Ancestry_matchGroups itself. See this FAQ for an example query.

FTDNA Tables

TableDescription
FTDNA_Matches2Primary Family Finder match table: match identity and names, contact, relationship range, total and longest shared cM, Y-DNA/mtDNA markers and haplogroups, and tree URLs.
FTDNA_ICW2In-Common-With (shared match) pairs between two of your matches.
FTDNA_Chromo2Chromosome-browser segment data (chromosome, start/end position, cM, SNPs) per match.
FTDNA_TreeFamily tree individuals from matches’ linked trees: person details, parents, haplogroups, and pedigree links.
FTDNA_KitStored FTDNA account/kit login credentials (internal).
FTDNA’s current tables are the …2 variants (FTDNA_Matches2, FTDNA_ICW2, FTDNA_Chromo2). The older non-suffixed tables are legacy and are no longer written by current builds.

23andMe Tables

23andMe tables use the MeAnd23W_ prefix and are keyed per profile by psid (the 23andMe profile ID).

TableDescription
MeAnd23W_KitStored 23andMe account/kit login credentials (internal).
MeAnd23W_Profiles23andMe profiles available under the account (profile id, name, source).
MeAnd23W_RelativesDNA Relatives list — comprehensive per-relative data: names, predicted relationship and range, shared DNA and segments, haplogroups, ancestry composition, locations, and sharing/contact status.
MeAnd23W_MatchesMatch records gathered for a profile (relative identity, relationship, shared DNA, haplogroups).
MeAnd23W_ICWIn-Common-With pairs with shared cM and percent shared.
MeAnd23W_TriagTriangulation flags between two relatives for a profile.
MeAnd23W_FIANewShared DNA segments (Family Inheritance: Advanced): chromosome, start/end, genetic distance, SNPs.
MeAnd23W_FamilyTree23andMe family tree nodes: relationships, parents/partners, generations, and flags.
MeAnd23W_SharesShared/connected datasets for a profile (guid, name, source).
MeAnd23W_HaploHaplogroup sharing between you and a relative.
MeAnd23W_AncestryCompSummaryAncestry Composition summary: population percentages by threshold.
MeAnd23W_AncestryCompSegmentsAncestry Composition painted chromosome segments per population.
MyHeritage and GEDmatch gathering is currently unavailable in the Client and will return in a future update; these tables are documented here for databases that already contain gathered data.

MyHeritage Tables

TableDescription
MH_MatchPrimary match table: identity, estimated relationship, shared cM/segments, tree info, surnames, and per-step gather dates.
MH_ICWIn-Common-With pairs with shared cM, percent, and triangulation totals.
MH_ChromoShared chromosome segments between two kits (chromosome, cM, start/end, SNPs).
MH_TriangulateTriangulated segments among a kit and two matches.
MH_TreeMatch tree references (tree URL, created/updated dates).
MH_AncestorsTree individuals (ancestors) from match trees.

GEDmatch Tables

TableDescription
GM_KitKit registry: kit number, name, sex, haplogroups, and WikiTree linkage.
GM_MatchOne-to-one match list between two kits (shared/largest cM, generations, run dates).
GM_SegmentShared chromosome segments between two kits.
GM_ICWIn-Common-With pairs with total shared cM.
GM_TriangulatedSegmentAutoSegment triangulated clusters — overlapping segments on a chromosome shared by multiple matches.
GM_CommonAncestorCommon ancestors identified from match trees (from ClusterDisplay data).
GM_CommonLocationLocations shared across match trees.

DNAGedcom Tree

The unified, service-independent family-tree store. GEDCOM uploads and gathered match trees are normalized into these tables so the People and Common Ancestor tools can compare trees across services.

TableDescription
DGTreeTree records: name, tree id/URL, base person, source, and the linked match (if any).
DGIndividualIndividuals within a tree: names, dates, places, parents/spouse, and ahnentafel relationship id.

Shared & Core Tables

Cross-service and internal application tables that are not tied to a single testing company.

TableDescription
DNA_KitsUnified kit registry across all services (company, guid, name, role).
DNA_KitSummaryPer-kit summary counts (matches, ICW, chromosomes, surnames, ancestors, trees).
DNA_LoginCross-service login credentials (internal).
DNA_TagUser tags/labels applied to tests or matches.
DNA_ProcessRecord of each gather run (parameters, results, options gathered, cM range).
DNA_ScheduleScheduled recurring gathers (internal).
Gather_HistoryHistory of gather requests with timing and cM metrics.
SettingsApplication key/value settings (internal).
Kit_TreeAssignmentAssigns a tree (GEDCOM or a service tree) to a DNA kit.
Match_TreeOverrideOverrides a match’s gathered tree with a better tree (e.g., a GEDCOM upload).
Computed_CommonAncestorsCached common-ancestor results from pairwise tree comparison.
Computed_AncestorStatusPer-kit common-ancestor computation status (last run, counts).