Forum Moderators: open
I would need to access the db on every hit of my site to determine what image to display....I have an image on each page of a small 80 page site that needs to change depending on time and day, 5 times a day. I have to search a table with 35 rows with columns for images, start and stop times, and a link.
Is that too much server activity for a mysql db?
It seems like a lot but I’m new to this and really have no idea what a db is capable of.
(I am on a basic shared hosted server, and the site gets only about 2000 unique visits a day, and another small table in the same DB is being accessed frequently as well for another page)
I am using just a PHP page to do this now but need to be able to change the images and times easier so wanted to try using a db.
Thanks for any insights or reference links!
MySQL has come a long way.
I suppose then another table in the db I was concerned about shouldn't be a problem either? - it's very little data but getting written to frequently - every 3-5 minutes, as well as displaying all it's contents (couple hundred lines) on the most popular page of the site (1500 times a day, 7000 for yet another table for client's other site)
These two tables have been running OK for months but I've wondered if i was pushing it, and now adding this other table might be too much?