I am converting one of my websites to be database driven.
The big pro is that I can spend more time developing the
site and less time updating the site. As an example, on the
home page it shows the next 5 events scheduled on the
calendar. Non db version of the site had me updating the
page anytime an event passed. DB version uses a query to
pick the next 5 events based on the date. The table driving
it was a simple export from the Outlook Calendar. Makes
that easier. If you are selling products, they can all be
stored in the db with links to the images. You would only
need to create 1 page which would take the info from the db
and use that in the page. Non DB version would be a page
for each item
The only real con to this approach is that the server
will be accessing the db every time a request is made, and
then it would put the page together. This is not an issue
if you only have a few users and small tables. What can be
done to help alleviate this is to use system variables for
the information which will reduce the need to access the db
Home Page example:
http://www.lannonfire.com
Mike
message : I have been commissioned to re-make one of our companies
: internal websites. It has been mentioned that I might
: want to look at making the new one database driven.
:
: Anyone have any pros and cons for creating a new website
: using a DB?
:
: Thanks,
:
: BrianR
