Desktop

Ask something
Question Locked

Mysql on the desktop

0 helpful
5 replies

by misterbill63 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Is it possible to use PHP/MYSQL in a local network business enviroment. I have been using a WAMP installation on my local network of three computers and wondered how it would perform under a heavier load. How would it compare speed wise compared to Access or Filemaker for instance.

Thanks

5 replies

by robo_dev

MYSQL compares very favorably with Microsoft SQL server, and even Oracle from a performance standpoint.

While MS Access begins to have performance issues at five users, for MYSQL or MS-SQL, those issues tyically happen at well over 100 simultaneous users, and MYSQL can be scaled up and up and up..Alcatel manages 60 Million subscribers on a MYSQL database cluster.

http://www.mysql.com/why-mysql/case-studies/

My understanding of Filemaker is that it's essentially like Microsoft Access for the Mac platform and is not intended to be a multi-user database.

by tony hopkinson

Operational issues might be a concern, for instance you need to do a reboot, after an install.
Also anything you do that is major resource hog, such as video / image editing, might have a performance impact.

If you expect to grow and you want to hive it off operationally, a dedicated average desktop should more than do the job.

by misterbill63

Thanks for the replys. At the moment i am using a web browser as the user interface which works well for me on my small network. Would this be usable on a larger network in day to day business or am I way off course. Mysql/PHP seems to mainly used on websites and not on the desktop and i wondered if was right for the job.

by tony hopkinson

actually tends to work very well.
Access fails as a multi user system because it's not client server. IIS (presumably) most definitely is, so access only sees one user and all it's weaknesses in this regard are obviated. It's a very elegant solution until the database slows down due to volume or complexity.

Swapping out access as a backend for SQL Server tends to be trivial, even shifting to MySQL isn't too off putting, should it become desirable.

I've talked to guy one here who does this a lot and he said he got acceptable performance on 50 users and 100s of megabytes of data. No experience of it myself as I tend to do big systems.

As always with client server, the trick is to get in and out quick, minimising the amount of time data is locked.

This discussion is closed to new replies.