Main table with hundreds versus a few smaller ones

I was wondering which approach is better for database development?

I currently have one large table (97 columns per row) with links to lookup tables where I could.

Wouldn't it be better for performance to group some columns into smaller tables and add key columns to them to refer to a single whole row?

+5
source share
3 answers

If you divide the table into several parts, you will need additional joins to get all the columns for one row - it will cost you time.

97 columns are not very, in fact - I saw a path beyond 100.

, - 97 , 97 , .

, :

  • "" (, XML, VARCHAR(MAX) ..) , → , "" " , -

  • , , . , "" , . 20% - 80% , .

+3

, . SQL Server . , , . , . ( > 1% ), 97 , , , . , , , , , , .

0
source

All Articles