This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have a hotel management system I created based on Lightspeed and SQL Server 2005, now one of my customers insists on using MySQL on a Linux Server as his back end. Our SQL database is only used for tables and, stored procedures for reports. Using pretty standard data types, i.e. nvarchar(), int, float, money, image (photos), bit (boolean), etc. What I want to know is, are there any known problems I might run into when converting my database to use MySQL, and using my LightSpeed model to create the tables, or with my exiting API and LINQ queries? And also, although strictly this may not be a question for you guys, but I welcome any advice, how reliable / stable, is MySQL on linux compared to SQL Server on Windows Server 2003. Can I expect lots of support calls? As you probably gathered, I have never used Linux or MySQL before. :-S
|
|
|
Generally, our experience has been that MySQL is pretty free of surprises and we have been able to maintain mostly the same feature set over MySQL and SQL Server. Looking through our test suites, the only places where capabilities or behaviour vary between MySQL and SQL Server seem pretty minor (e.g. MySQL Average method returns floating point values rather than integers, MySQL does not support Intersect, some differences in string handling). Of course what we consider a minor feature might be something crucial to you so of course you will need to test thoroughly! Please note I'm talking only about LightSpeed support here -- there may be other considerations in porting the database schema and particularly stored procs. For example, I am pretty sure MySQL doesn't have a money type but you should be able to use a fixed-point numeric type for that (I don't think it has a bit type either but TINYINT(1) does the job). Also, I seem to recall that MySQL on Linux is case-sensitive with regard to table names (can't remember about column names), whereas SQL Server and MySQL on Windows are not. (I also vaguely recall it might default to a nontransactional database engine, but I could be wrong about that.) If you have a .lsmodel file then that should be able to create a decent first stab at the MySQL schema which should be enough for you to do some quick preliminary "sanity check" smoke testing before you decide yes or no. We can't comment on MySQL/Linux reliability or other operational issues. I know we have customers using that combination to run real-world Web sites but I don't know how their nonfunctional requirements compare to yours. Good luck! |
|
|
Thanks for the feedback. Greatly appreciated. If we move ahead with this, I will let you know the results, in case anyone else wants to try it.
|
|