Printable View
We represent a large company that has a product for managed file transfer. The product used MySQL for locally storing configuration. Soon after Oracle acquired Sun, the company switched their entire product line from using MySQL to SQL Express. Rumblings indicate that they do not want to deal with any future license complications. Anyone picked up any other trend like that regarding MySQL?
It doesn't sound like smart move at all - while MySql is practically has no limits and very fast MS Sql Express is limited to 4GB. Also, not all functionalities are available in Express.
Also (and this is just a thought), if your company is marketing their product then they should be flexible to any database what so ever but specifically major ones.
If the purpose is storing local configuration I doubt a limitation of a couple of GB is going to be a problem.
I can't imagine using MySQL for something of that sort anyway though. You'd be better off I would think using an embedded database technology. Windows has Jet 4.0 (Jet Red) and ESE (Jet Blue) out of the box, or you might look at something like SQLite as an alternative. Even SQL Server Compact Edition is a less intrusive choice than SQL Server Express.
Service-based DBMSs don't work well as a local datastore. You have to watch out for instance conflicts, users disabling the service, etc.
The application stores local configuration - any local database technology would do the job including MS Access. What took me by surprise is the fact that they dropped MySQL not for technical but for possible future licensing issues.
As far as I am aware MySql will continue to be open source so it's free. What you pay for is support only but how often did they have to call for support in the past?
The answer is probably "never". After all it's their business so let them struggle. :)