I have run an analysis with SchemaSpy.
The tool gave me a warning message for two tables. The warning message is:
Tables with incrementing column names, potentially indicating denormalization
What is meaning of the above error?
For reference :
The meaning of this anomaly warning message
database-designschema
Related Question
- Why wouldn’t I put the single preferred option into its own table, instead of having a ‘Preferred’ column
- Is this the correct way to model a relationship between an object which may or may not have another object
- Oracle 12c – Unable to Install Sample Schemata on Windows 10
- Database Lookup Tables – Best Practices for Relational Databases
- SQL Server – Create View with Column Aliases or Change Column Names
- Postgresql: there is no unique constraint matching given keys for referenced table
- Sql-server – Foreign key referencing table with composite primary key when I only need 1 column association
Best Answer
Based on the sample table in your link, I'd suggest it's taking issue with fields such as:
or
This may indicate a design flaw (but not always), and if so, one that can probably be corrected by more descriptive field names or perhaps a child table.
For example, someone might have more than one phone number... what if someone has three? Seven? Maybe data like this should be in a subtable, and perhaps even with some sort of indicator of what type of phone number it is, whether it's a preferred phone number, etc. Alternatively, maybe just renaming the fields to
phone_homeandphone_cellwill be enough to eliminate confusion and allow you to collect all of the data you need.