Page 1 of 1

mysql database vs mssql server

Posted: Sun May 06, 2012 2:53 pm
by cali_dotcom
hi, i am currently building an application that depends on a third party application written in .net using a mssql server database. i am more of a lamp guy and prefer mysql. to extend the application i would need to add some tables to the database. i am currently thinking of creating my custom tables in mysql instead of adding new tables to the mssql db. i currently have to use free tds to communicate with the mssql da and that creates some challenges. is it better to leave the third party application alone using free tds to communicate with it and then create a new mysql db for my tables or to just have all data in one database, namely mssql, and just use free tds to communicate with all data? i would have to write an api to communicate with the db and also prefer to have this in php rather than .net.

Re: mysql database vs mssql server

Posted: Mon May 07, 2012 11:46 am
by x_mutatis_mutandis_x
cali_dotcom wrote:hi, i am currently building an application that depends on a third party application written in .net using a mssql server database. i am more of a lamp guy and prefer mysql. to extend the application i would need to add some tables to the database. i am currently thinking of creating my custom tables in mysql instead of adding new tables to the mssql db. i currently have to use free tds to communicate with the mssql da and that creates some challenges. is it better to leave the third party application alone using free tds to communicate with it and then create a new mysql db for my tables or to just have all data in one database, namely mssql, and just use free tds to communicate with all data? i would have to write an api to communicate with the db and also prefer to have this in php rather than .net.
Is there any relational dependency between the tables you are adding and the tables existing in your sql server db? If so, it's better you add tables to the sql server db so you can normalize them. If there is no relationship, and the data in your app doesn't require normalization with the tables in your sql server, go for mysql DB. Either ways, when you code it in PHP, look into PDO as it supports multiple drivers to connect to different DB platforms.

Re: mysql database vs mssql server

Posted: Mon May 07, 2012 1:48 pm
by tr0gd0rr
If I were your successor, I would prefer to have all the data in one place. I imagine a DBA would feel the same way. Even if there was no data in the MSSQL server, I can't think of a compelling reason to use MySQL if you have a MSSQL server all ready to go.

MySQL is arguable a bit easier to manage for novices, but I assume you already have a DBA for your MSSQL server.