Skip to Content.
Sympa Menu

internetworkers - Re: Database inquiry

internetworkers AT lists.ibiblio.org

Subject: Internetworkers: http://www.ibiblio.org/internetworkers/

List archive

Chronological Thread  
  • From: mdthomas AT mindspring.com
  • To: InterNetWorkers <internetworkers AT franklin.oit.unc.edu>
  • Subject: Re: Database inquiry
  • Date: Wed, 12 Sep 2001 16:00:42 -0400



A couple of questions:

- What kind of workflow surrounds the Access DB now?
- How is the data in the DB needed for your web site?
- What size is the DB now and is it expected to grow
in size?
- What kind of network connectivity do you have with
your host site, and what kind of applications/DB support
are they willing to offer?


If the DB is updated a lot and you want the updated
info on the web site immediately, you'll probably
need to move to some other kind of DB that lives
with your web server and also supports your internal
DB work. This means that you'll have to interface
with the DB over the network from your office, possibly
over the web.

If the data is basically read-only from the web site
point of view and the data is seldom updated, you
could get away with some kind of manual update solution.
Maybe an XML db dump that your appserver (middle
ware) loads on start. If you find later that you need
a solution like above, you can use the same code to
process the XML on the front side and add code to
create the XML dynamically on the back side.

Third possible solution: Have a DB at your host
site that you sync up with your local DB. With
this solution, you can maintain your current
workflow around the Access DB and still have a
proper AppServer set up at the host site without
having to interface to the host site. Your data
might get a little stale, though, depending on
how often you synchronize. You could probably
do it once an hour or so, though.


InterNetWorkers <internetworkers AT franklin.oit.unc.edu> wrote:
> My office would like to have a database-driven site. We're in the
preliminary planning stages and need a few questions answered, if anyone has
the expertise and the time to explain it to me so I can explain it to
them!!!

1. What exactly do we need? We have a database set up right now that is part
of a proprietary program for Convention and Visitors Bureaus, but could be
mapped into Access. The Internet person (me right now; someone new in a
month and a half) has a Mac. Our site is hosted by a hosting company and I
BELIEVE their servers are Unix, although that would have to be confirmed.

I know we need some sort of middleware, but is it better to stick with MS
and use the Access database along with some ASP, or should we start from
ground zero? Should my job as the sole Internet person have a Mac or a PC,
or will that matter? I'm pretty sure the middleware goes on the server, so
would a hosting company provide that, or would we have to move our server
in-house? And if they have Unix servers, does that eliminate using the
whole Access/ASP option if they continue to host our site?

I think that should get us started on our discussion. Thanks in advance for
any help you can offer.
---
Mary Beth Lackey
Internet Manager
Greater Raleigh Convention and Visitors Bureau
http://www.raleighcvb.org



---
Come and play at the InterNetWorkers Web site!
http://www.ibiblio.org/internetworkers/
You are currently subscribed to internetworkers as: mdthomas AT mindspring.com
To unsubscribe send a blank email to $subst('Email.Unsub')





Archive powered by MHonArc 2.6.24.

Top of Page