Thanks guys! I'm really curious about anything OpenBD related that can help out with the replication, etc.
>From what I was thinking to start, I would have two Database servers, and one simply replicated to the other. If there was a failure, I'm not quite sure how I'd manage switching data sources. Thoughts? On Tue, Jan 3, 2012 at 9:53 AM, Alex Skinner <[email protected]> wrote: > Check out http://xeround.com/ > > I've been trying this its replicated Active / Acrive MySQL in the > cloud > > I've not managed to get the JDBC failover stuff working yet but I > think thats a bug im just testing from Java to confirm > > A > > On Jan 3, 3:32 pm, 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 > -- 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
