| Goal | This query identifies base table columns participating in a PRIMARY KEY, UNIQUE, or FOREIGN KEY constraint whose names suggest they store surrogate key values (having an id prefix or suffix), yet are defined with a data type other than an integer type (smallint, integer, bigint) or uuid. Surrogate keys are system-generated identifiers carrying no business meaning and should be stored using compact, fixed-width integer types or native uuid values. Storing surrogate keys as text (varchar, text) or numeric types increases storage overhead, introduces unnecessary string collation costs, and slows down index lookups and table joins. |
|---|---|
| Type | Problem detection Each row in the result could represent a flaw in the design |
| Reliability | Medium Medium number of false-positive results |
| License | MIT (opens in new tab) |
| Data Source | INFORMATION_SCHEMA+system catalog |
| SQL Query |
|
Fixing Suggestion
numeric types to an integer type (integer/bigint) or uuid for better storage efficiency and join performance. If the column intentionally stores an external natural identifier (like national_id), consider renaming it (e.g., using a _code suffix) or excluding it. Collections
This query belongs to the following collections:
Find problems automatically
Queries, that results point to problems in the database. Each query in the collection produces an initial assessment. However, a human reviewer has the final say as to whether there is a problem or not .
| Name | Description |
|---|---|
| Find problems automatically | Queries, that results point to problems in the database. Each query in the collection produces an initial assessment. However, a human reviewer has the final say as to whether there is a problem or not . |
Categories
This query is classified under the following categories:
Data types
Queries of this category provide information about the data types and their usage.
Result quality depends on names
Queries of this category use names (for instance, column names) to try to guess the meaning of a database object. Thus, the goodness of names determines the number of false positive and false negative results.
Validity and completeness
Queries of this category provide information about whether database design represents the world (domain) correctly (validity) and whether database design captures all the information about the world (domain) that is correct and relevant (completeness).
| Name | Description |
|---|---|
| Data types | Queries of this category provide information about the data types and their usage. |
| Result quality depends on names | Queries of this category use names (for instance, column names) to try to guess the meaning of a database object. Thus, the goodness of names determines the number of false positive and false negative results. |
| Validity and completeness | Queries of this category provide information about whether database design represents the world (domain) correctly (validity) and whether database design captures all the information about the world (domain) that is correct and relevant (completeness). |
Further reading and related materials: