Browse DevX
Sign up for e-mail newsletters from DevX

Tip of the Day
Language: SQL Server
Expertise: Beginner
Mar 24, 1997



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Normalized Database: When to Split?

We have several heavily-used tables with lots of columns (average around 30 columns), and the users are getting locked out frequently. We've thought about splitting the tables, but didn't want to sacrifice all the work we put into normalizing them. Any thoughts?

Although normalized databases are the ideal in theory, sometimes it is necessary to de-normalize. If you can split the larger tables into two or more smaller tables without duplicating information (except for the primary key, of course), that would be ideal. But if you have to duplicate some information, make sure that you grant update and insert privileges of that data in only one table. I know it's hard to de-normalize after going through the normalization process (all that work!), but if you start with normalized databases, and if you take care to protect the data integrity of any duplicate columns, you would be able to re-normalize easily if it were ever needed (and a simple join or view can recreate the appearance of the normalized data).

DevX Pro
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date