Web Hosting Talk







View Full Version : Access Database


Eiolon
04-23-2005, 09:46 AM
I know Access is a flat-file database so I was curious how much is too much in terms of usage before a shared host would throw you off the server? I am working on something and it is up for testing and right now I already have about 100 unique hits per hour on it. Should I think about converting to MySQL?

I'd like to have as little cost as possible so getting a VPS or Dedicated Server isn't something I'd want to do at this point.

Eiolon
04-23-2005, 03:51 PM
Okay, I've decided to convert to MySQL just because I need to learn it any ways.

I have installed MySQL Server and started a database. I created a new user for myself. I went to install and connect with my OBDC driver and everything connected fine.

However, I am also using ColdFusion so when I go into the CFAdministrator to supply the datasource it says that it cannot find a connection to the server. I have tried both localhost and 127.0.0.1 and I still get the same error. Yet when I go into the OBDC I can connect to the database fine.

Any suggestions?

GrindKore
04-23-2005, 07:37 PM
Originally posted by Eiolon
I know Access is a flat-file database so I was curious how much is too much in terms of usage before a shared host would throw you off the server? I am working on something and it is up for testing and right now I already have about 100 unique hits per hour on it. Should I think about converting to MySQL?

I'd like to have as little cost as possible so getting a VPS or Dedicated Server isn't something I'd want to do at this point.


Access is actually a relational database, flat file databases are basically a CSV formatted text file or an Excel sheet.

As far as load for shared hosting, it all depends on coding, size, and index structure of your database and the way your web application accesses data. Some of my clients have Dot Net Nuke installations with over 3000 registered members and the loads are still with in acceptable parameters. Others code poorly and forget to close database connections or let their recordsets run in dead loops, in those cases even one hit is one too many.