>We're having a discussion as to what SQL database to target if we convert to SQL.
>
>MySQL: The price is right, plus customers can deploy to Windows or Linux if they like. One problem is some of the larger customers we deal with want MS SQL. They either have existing databases and have the staff to support MS SQL, or they are Microsoft-only shops. So if we go with MySQL we also have to support MS SQL for larger installations.
>
>SQL Express: The price is also right. Also, we have an apparently easy migration path to SQL Workgroup or Standard, if need be. It seems like we can write once for SQL express and it will work with Workgroup or Standard. If I'm reading it right, Express will only use 1gb of RAM and 1 CPU, and the database is capped at 4gb. 4gb is big enough for most of our small/medium customers.
>
>Ours is a POS application that puts an intermittent load on the database, we don't load the database continuously like a web app would. Our smallest installations are 1-5 clients, and our largest is 200 or so. It feels like we could ship with SQL Express to most customers, and larger customers would purchase Workgroup or Standard if SQL Express gets bogged down.
>
>Any thoughts?
>Chris

You understand that with MySQL your application also has to be Open Source, otherwise you need to buy a license for MySQl.

For Open Source Projects:
If you are developing and distributing open source applications under the GPL License, then you are free to use MySQL under the GPL License. More Info »
If you are developing and distributing open source applications under an OSI-Approved License, but not the GPL, MySQL provides the GPL License with a FLOSS Exception. More Info »
For Commercial OEMs, ISVs and VARs:
For OEMs, ISVs, and VARs who distribute MySQL with their products, and do not license and distribute their source code under the GPL, MySQL provides a flexible OEM Commercial License. More Info » .Signature { margin-top: 12px; color: #666666; } .Signature a { color: #666666; }