|
|
|
SSC-Addicted
 
Group: General Forum Members
Last Login: Friday, October 30, 2009 6:46 AM
Points: 430,
Visits: 626
|
|
We are a Microsoft SQL Server shop when it comes to our database systems, but now word has reached the DBA area that one of our top executives is interested in a product that uses MYSQL. I know nothing about MYSQL outside of it being open source and would like to know the risks of using it. Hopefully I can find enough information to indicate it should not be considered for our company. In the meantime I'm going to search Google.
I appreciate your insight.
Thanks, Dave
|
|
|
|
|
Old Hand
Group: General Forum Members
Last Login: Thursday, July 16, 2009 2:38 PM
Points: 371,
Visits: 755
|
|
| Since there are not many details posted about particular requirements, I would assume that the most danger is in the learning curve of using Linux and MySQL in Windows and SQL server shop.
|
|
|
|
|
SSC-Addicted
Group: General Forum Members
Last Login: Friday, October 30, 2009 6:46 AM
Points: 430,
Visits: 626
|
|
No issues in the areas of performance and reliability?
|
|
|
|
|
Old Hand
Group: General Forum Members
Last Login: Thursday, July 16, 2009 2:38 PM
Points: 371,
Visits: 755
|
|
Dave,
MySQL market share is ~30%. It's used mostly in a small Web faced application.
If you are talking about a stand alone application then I am not aware about any issues other than I stated (and it is a valid risk that you should estimate and translate to the budget money). If you have additional requirements, like implementation of MySQL in any data flow, then of course you will have additional issues.
|
|
|
|
|
SSC-Addicted
Group: General Forum Members
Last Login: Friday, October 30, 2009 6:46 AM
Points: 430,
Visits: 626
|
|
Sounds like our DBA team won't be able to offer any arguments against it.
Thanks for the quick response.
Dave
|
|
|
|
|
SSChampion
Group: General Forum Members
Last Login: Today @ 11:32 AM
Points: 14,521,
Visits: 10,409
|
|
The main problem I would see is the learning curve. MySQL can run on windows, but it will still require some time to get familiar with the admin requirements and the flavour of SQL language that it uses.
What kind of app is is that the boss wants to buy?
Why do you not want to use MySQL?
Gail Shaw
We walk in the dark places no others will enter
We stand on the bridge and none may pass
|
|
|
|
|
SSC-Addicted
Group: General Forum Members
Last Login: Friday, October 30, 2009 6:46 AM
Points: 430,
Visits: 626
|
|
It's a quantitative analysis application. Our only objection is that we are introducing a new RDBMS into the company and want to make sure there are no major risks associated with it. From a cost-benefit analysis perspective I need to determine how much time the DBAs would need to spend on this RDBMS vs. Microsoft SQL Server, where we already have an established knowledge base. From what I have been told the database is built into the application and there is nothing for us to maintain. I need to see the technical specs to confirm that, however. My questions are "what about backups, performance tuning, security..." All of the basic questions.
Thanks, Dave
|
|
|
|
|
SSChampion
Group: Administrators
Last Login: Yesterday @ 4:33 PM
Points: 21,728,
Visits: 5,982
|
|
The danger is knowledge.
MySQL is used by Yahoo and some other huge clients. Sun now supports it and it runs great in all sizes of companies. It has a modular architecture so you can plug in different storage engines, add transactions, etc.
It's a solid database, but it doesn't have all the bells and whistles of SQL Server (SSIS, etc). Backup / restore work well, various DR add-ons, but they work fundamentally different than SQL Server, so you need to keep up knowledge in two areas, test plans twice, etc.
Nothing wrong with using it if you have the skill sets (or can get them.)
|
|
|
|
|
SSC-Addicted
Group: General Forum Members
Last Login: Friday, October 30, 2009 6:46 AM
Points: 430,
Visits: 626
|
|
|
|
|
|
Hall of Fame
Group: General Forum Members
Last Login: Thursday, October 01, 2009 1:21 PM
Points: 3,135,
Visits: 188
|
|
A word of warning - not necessarily against MySQL, but against applications with 'built-in' databases.
Check the SLA very closely. Some companies say that you have to do everything through their interface and if you do 'real' DBA work it violates the SLA and any warranties. I have dealt with this at other companies that I worked at. One application had MySQL and the other Oracle. We couldn't 'DBA' either of them and could only use the application to take care of the databasess. Want to delete data? Don't use commands or anything else - do it through their GUI or else.
Another application we had at my first job had SQL Server built in and the company had an interface that maintained the databases. However, they were very allowing of true DBA's to maintain the databases with SQL Server tools. They worked very closely with me since they knew I was a DBA and knew what I was doing.
-SQLBill
|
|
|
|
