I recently posted a similar post, but I don\'t think I included nearly enough info. So here it is again with all the details...
MySQL DB
Expected rows in DB at peak: 25,000
Fields in each row: About 75
Which one of these will be the easiest on server resources?
1.
=====
Have each field in the DB contain a code number (usually a one digit int), and then convert that code to useable data with PHP.
Example: The \"Location\" field has a value of \"1\", and the PHP uses \"if Location == 1 then echo \'building one\', else if...\".
2.
=====
Have each field in the DB contain useable data, and the PHP just pulls that.
NOTE 1: All this \"useable data\" I speak of in both 1 and 2 has an average length of 10 characters.
NOTE 2: Up to 5,000 searches could be performed on this DB per day at peak.
NOTE 3: Besides the searches, up to 9,000 individual pages using all of the fields (again, about 75) as the content could be loaded per day at peak.
MySQL DB
Expected rows in DB at peak: 25,000
Fields in each row: About 75
Which one of these will be the easiest on server resources?
1.
=====
Have each field in the DB contain a code number (usually a one digit int), and then convert that code to useable data with PHP.
Example: The \"Location\" field has a value of \"1\", and the PHP uses \"if Location == 1 then echo \'building one\', else if...\".
2.
=====
Have each field in the DB contain useable data, and the PHP just pulls that.
NOTE 1: All this \"useable data\" I speak of in both 1 and 2 has an average length of 10 characters.
NOTE 2: Up to 5,000 searches could be performed on this DB per day at peak.
NOTE 3: Besides the searches, up to 9,000 individual pages using all of the fields (again, about 75) as the content could be loaded per day at peak.