I don't think I can answer all your questions as I use Linux.
Are you sure it was the DB that went down or their whole system crashed? I
can believe the latter more than the first. Ever since I switched from
Windows to a unix based system, I have had far less troubles with the server
crashing. In fact, I've only had my Linux down a couple of times... and
that was for maintenance only, unlike the Windows server where it used to
crash once every couple of weeks for no apparent reason.
Maybe that crash will convince your customers to switch to a unix based
machine. With only 3 - 5 clients, I can't imagine it seeing very heavy use.
How many queries per second?
128Mb works fine on my unix server, but in the past, I've found Windows to
be more resource hungry, so, if I were you, add more memory even as much as
500Mb. But again this all depends on what you are running and the amount
traffic you're getting.
----- Original Message -----
From: "Lee Jenkins" <[EMAIL PROTECTED]>
To: "MySQL Mail list" <[EMAIL PROTECTED]>
Sent: Friday, April 20, 2001 10:24
Subject: In need of urgent Advise, please
>
>
> Hello,
>
> First, sorry the lengthy post. I have a couple of questions that are very
> important for me to get answered. I we moved from using MS Access to
MySQL
> for our Point of Sale app. We do the transaction rollbacks, commits in
the
> application layer so the fact that MySQL lacks this functionality is no
> problem especially when compared to the speed that we get from the DB.
>
> We would very much like to run MySQL on a Linux box, but when our
customers
> (many lack even basic Windows skills) hear the word Linux, they run for
> cover. They obviosly don't know how stable it is, only that Windows gives
> them a nice fuzzy warm feeling. So, we are deploying the Windows Version
> of MySQL running on Win2K Prof or Server depending on how many POS
stations
> will be hitting the DB. We're using MyODBC to talk to the server with ADO
> from VB60 apps running on Win98 Clients.
>
> Last night, I had a customer whose DB went down and got very corrupted.
> It's only got 128 MB RAM on it and in addition to running the MySQL NT
> service, it's spooling a lot of print jobs to remote receipt printers for
> the kitchen/bar, etc and running the Credit Card Payment software too. I
> warned them that I thought 128 MB RAM was not enough and that is my guess
> as to why it went down (plus the server had not been rebooted in about a
> week).
>
> At any rate, I have 2 very important questions that I really need to get
> answered and am grateful for any responses.
>
> # 1:
> Considering that we have an average of 3-5 clients hitting the database
> with SELECTS, INSERTS and UPDATES sometimes pretty heavily, would 256 MB
> RAM suffice on a LAN?
>
> # 2:
> What, if any, parameters should I setup in the MySQL server for maximum
> efficiency?
>
> # 3:
> If we start the MySQL server with update logging, I see the files that it
> creates each time it is started. In the case of a crash, how would I go
> about restoring the database from the logs on Win2K? I've looked in the
> manual, but don't quite understand the syntax to do this or even if it's
> the same for Windows. Could someone please give me the Romper Room level
> lowdown on doing that?
>
> Again, I don't look forward to having another all-nighter like last night
> so I would be very, very grateful for help on these things. I like MySQL
> and the support found here in the list and very much want to keep using
it.
>
> Again, thank you in advance.
>
> Lee
>
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
