>> Is there any glaring reason NOT to move to mySQL? Playing devils advocate: Yes. http://www.mail-archive.com/[email protected]/msg339871.html
As always YMMV, and you may never have these sorts of issues (I haven't), but I have ran into a similar predicament in the past with FOSS. That said, David's post is always in the back of my head when making these sorts of decisions. G! On Jan 3, 10:32 am, Jason Allen <[email protected]> wrote: > Hi Guys, > > I'm trying to make a decision on whether I'm going to stay with > Microsoft SQL, or move to mySQL. > > I'm building an app, and while it has many tables and databases, the > tables themselves aren't anything special and so far I haven't seen > any reason I couldn't port them to mySQL very easily. I'm not locked > into any stored procedures or anything. My app's SQL language is very > straight forward and nothing too complicated. I'm sure I'll have to > rewrite some of the queries but they all work as is so it shouldn't be > hard to make the switch. > > My issue is really cost. I want to setup the app so that the database > has redundancy and replication. I can launch on SQL Express to start, > since it's free, but that doesn't offer anything in the ways of > replication, etc. Once I get into some serious real time replication > and clustering, I need SQL Enterprise, and it's very expensive for a > single CPU license. > > With mySQL, I'm not bound by licensing costs, and the 'free' version > comes with replication out of the box. A coworker of mine is very > experienced with managing mySQL, including setting up clusters, > replication, etc. and he's willing to help me get it all setup. > > My thoughts are, if I get the mySQL cluster setup right from the > beginning, I'm launching with a much better infrastructure and > disaster recovery plan. It would cost me thousands of dollars in > licensing to get this same setup with MS-SQL, and that would just be > for single CPU licensing. If I saw any kind of growth, especially if > it was fast, the licensing costs could soar above $100,000 quickly. > I'd rather spend that money on hardware and paying an admin to help me > manage a mySQL cluster. > > Since I'm using OpenBD, I'm asking this community on their thoughts. > Is there any glaring reason NOT to move to mySQL? I'm personally much > more versed with Microsoft SQL (certified) but it seems like a better > investment to move to mySQL. > > Thanks! -- online documentation: http://openbd.org/manual/ google+ hints/tips: https://plus.google.com/115990347459711259462 http://groups.google.com/group/openbd?hl=en Join us @ http://www.OpenCFsummit.org/ Dallas, Feb 2012
