Clone Tables

This smell occurs when a table is split horizontally in multiple tables using some criterion (for example, year) to achieve scalability.

This smell not only makes the querying difficult but also introduces problems managing data integrity.

Example

CREATE TABLE Bugs_2008 ( . . . );
CREATE TABLE Bugs_2009 ( . . . );
CREATE TABLE Bugs_2010 ( . . . );

Tools

The following set of tools detects this smell: DbDeo(for SQL)

Reference

B. Karwin, “SQL Antipatterns: Avoiding the Pitfalls of Database Programming”. Pragmatic Bookshelf, 2010.