|
| |
|
|
garyj
Posts: 38
Joined: 12/13/2001
From:
Status: offline
 |
Limits on MS Access file? - 12/16/2001 12:29:37
Anyone know if there are limits to the number of records your web can handle if you use MS Access as your DB connection?
If there are, what' s a better program?
< Message edited by Spooky -- 8/21/2002 1:11:08 AM >
|
|
|
|
garyj
Posts: 38
Joined: 12/13/2001
From:
Status: offline
|
RE: Limits on MS Access file? - 12/18/2001 17:27:58
In following through on these links, I learned fom some hosting companies that most commercial sites (such as mine will be) are hosted on Unix systems and use Perl scripting for most functions. They advised against using FrontPage for anything more than the layout/display. Is this your understanding, Spooky? If so, does that mean that even simple FP form handling is out?
Here's my situation: I'm building a fairly straight-forward sales site with a DB. There's nothing fancy about it, but I do have a large customer base (100,000+), so it has to stand up under heavy load. I now plan to buy an Perl/CGI e-commerce template to suit my needs. Does this sound like the right approach?
Do I need to steer clear of all functionality areas with FP? Even simple forms? What can and can't it do in this environment?
| |
|
|
|
garyj
Posts: 38
Joined: 12/13/2001
From:
Status: offline
|
RE: Limits on MS Access file? - 12/19/2001 19:16:20
Thanks -- I'll do what you say. How do I work around using FP's bots for form processing?
| |
|
|
|
garyj
Posts: 38
Joined: 12/13/2001
From:
Status: offline
|
RE: Limits on MS Access file? - 12/20/2001 12:03:52
I'm also curious about why you say that UNIX MySQL will 'give up the ghost' under heavy loads; it seems to be the DB of choice for UNIX-based hosts, from what I've seen.
| |
|
|
|
Mojo
Posts: 2441
From: Chicago
Status: offline
|
RE: Limits on MS Access file? - 12/20/2001 14:51:07
Errr.... I wrote a LONG post and my precious 2 year old girl was under the table and turned off the computer!
Anyhow - The shorter version...
There are many variables that affect the load capacity of a database. Too many to really get into here. So, I will paint with a broad brush.
First, MySQL beats Access in almost every catagory. Lets just get that out of the way.
Now, I have personally seen MySQL die with around 90 users. That was mostly the sites fault... they needed better code. The general opinion seems to be that when used heavy MySQL can handle somewhere between 250 and 400 concurrent users. An example of heavy use could be a popular discussion forum.
There are some examples of MySQL taking huge numbers of hits over time, but this can be deceiving.
Lets use Access as the example here:
If your just grabbing data and shoving it to the end user (just a simple "SELECT a, b, c FROM TABLE WHERE...")
you should be able to open the database, run the query, and close the database very quickly. The time depends on many things including how large the table is. With a small table the length of time would be VERY small < .1 of a second. Lets be very conservative and say .4 of a second and give you 25 concurrent users with the simple database call.
This gives you 62 users per second (we are really painting with a broad brush here, but the concept applies to MySQL also). If everything was steady you could handle 3720 connections per hour, 89280 per day, 624960 per week and almost 2 1/2 million per month. This is why if you look hard you can find sites that have big numbers generated from an Access database. Simple DB work and good programming.
MySQL starts with the ability to handle a higher number of concurrent users than Access and grows from there. But MySQL can't handle the 15,000 concurrent users we used in your example. It is just too many to handle on single server.
You said --
"it (MySQL) seems to be the DB of choice for UNIX-based hosts, from what I've seen.
This is true only when trying to win over Access users. MySQL works well on the Windows platform and given the choice, I would use MySQL over Access if concurrent users was a concern. If not, I would stick with Access. SQL Server 2000 does not work on UNIX platforms which is good for MySQL because it is not in the same class as SQL Server 2000.
The power house Databases for UNIX are:
SymfoWARE
Oracle
Oracle
Informix
Sybase
SQL Server is in the same class as the above databases. But, only on Windows.
Joe
Edited the spelling on at least one knucklehead error...
Edited by - jbennett on 12/20/2001 14:53:55
| |
|
|
|
garyj
Posts: 38
Joined: 12/13/2001
From:
Status: offline
|
RE: Limits on MS Access file? - 12/20/2001 16:57:08
Thanks, that helps a lot. What about working around the bots in FP form handling, as you suggested in your first post?
| |
|
|
|
Mojo
Posts: 2441
From: Chicago
Status: offline
|
RE: Limits on MS Access file? - 12/20/2001 17:36:25
On forms:
Remove the grey code that FrontPage inserts in the form. You will be left with the HTML that builds the form.
In the beginning of the form you will have something like:
<form method="POST" action="--WEBBOT-SELF--">
the line "action=" is where the form is pointing when you submit it. Change the --WEBBOT-SELF-- to reflect an actual address. Make sure it remains within the quotes.
To grab the form values you could:
myVariable = request.form("field_name")
You would do this on the page that you pointed the form to.
When you move away from the FP bots you have much more control and power at your fingertips, but you then have to learn ASP.
Joe
| |
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version 
k¥ 
Either way, you have to learn a little ASP or a little Perl. 