Database Schema SQL Rows vs Columns -


i have lot of databases relatively large amounts of columns ranging 5 300. each table has @ least 50,000 rows in it.

what effective way store data? presently data has been dumped indexed sql database.

it suggested me create 3 columns follows.

column name, column category, row id, row data.

example data male, 25-40, 145897, 365

would faster? slower? there better ways store such large , bulky databases?

i never updating or changing data. outputted 'datatables' dynamic table sorted, limited , ect. category column used break columns on table.

normalize db!

i have struggled "theory" long time , experience has proven if can normalize data across multiple tables better , performance not suffer.

do not try put data in 1 row hundreds of columns. not because of performance because of development ease.

learn more here


Comments

Popular posts from this blog

How to remove text and logo OR add Overflow on Android ActionBar using AppCompat on API 8? -

html - How to style widget with post count different than without post count -

url rewriting - How to redirect a http POST with urlrewritefilter -