MySQL Crash Diagnosis

For the second time in as many months, our MySQL Server crashed. We are =
on version 4.1.8 running under Windows 2000. Up until last month MySQL =
had run flawlessly for three years. I looked at the .err file for any =
clues, but was unable to find anything useful. I suspect the main =
problem is that MySQL runs on the same server as our IIS 5.0 web server. =
IIS crashes about every two weeks, usually MySQL is ok. However, I think =
IIS is sucking up memory on the server, so MySQL crashes because the =
server is low on memory. This is only a theory.

I could use some help trying to diagnose why this is happening and/or =
prove my theory. We have some who beleive we should abandon MySQL and go =
with MS SQL, I am opposed to doing this, but I would like to be able to =
diagnose and find out exactly why mysql crashed, and find a way to =
prevent this from happening in the future. Any suggestions on how I =
should go about this.

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org