Learn
duplicates
2 registry resources · 1 tutorial, 1 runbook · roadmap: Data Quality
What this topic covers
DE//AGENT currently lists 2 resources under duplicates: 1 tutorial, 1 runbook. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.
What you can learn here
Documented learning objectives across these resources:
- Count duplicates per key with one GROUP BY query — via Deduplicate records without rewriting the table
- Correlate the first duplicate date with a deploy — via Deduplicate records without rewriting the table
- Rewrite affected partitions instead of the whole table — via Deduplicate records without rewriting the table
Where this fits in the learning roadmap
These resources map to stage: Data Quality (2). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.
Compare the registry's options
Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.
| Resource | Type | Difficulty | Verification | Score |
|---|---|---|---|---|
| Duplicate records | Runbook | intermediate | community flags | 35.25 |
| Deduplicate records without rewriting the table | Tutorial | beginner | community | 34.15 |
How scores are computed: source quality score.
Where to start
Highest composite score first:
- Duplicate records score 35.25 — intermediate
- Deduplicate records without rewriting the table score 34.15 — beginner
Scores rank provenance, completeness and trust — read how verification works before adopting anything.
Good fits
Start here if you're new: Deduplicate records without rewriting the table.
Cautions and limitations
Security-flagged entries: Duplicate records (1 flag). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.
Production use cases
- Duplicate records — Row counts are inflated and metrics double-counted after a retry, a fan-out join or a backfill. details
- Deduplicate records without rewriting the table — Row counts are inflated and revenue double-counted after a retry or a fan-out join. Work the duplicate-records runbook: find the first duplicate date, correlate it with a deploy, d… details
Further study
Adjacent topics: data-quality (2 shared), idempotency (2 shared).
Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.
Full resource list
| Resource | Type | Score |
|---|---|---|
| Duplicate records | Runbook | 35.25 |
| Deduplicate records without rewriting the table | Tutorial | 34.15 |