John W Colby
jwcolby at gmail.com
Wed Feb 19 10:13:21 CST 2014
Well... we shall see. I have a custom written major application which talks to SQL Server. It uses BCP to export data out of SQL Server to files, and then uses BCP to import files back in to SQL Server. So I will have to replace that with whatever the MySQL equivalent is. I have to export databases containing hundreds of millions of records (and hundreds of gigabytes) into matching tables in MySQL. I have to build indexes. I have to research whether MySQL has compression, which I am using on my data to get it all to fit into memory. I have to build views matching the views I use in SQL Server. I have stored procedures that perform tasks for me. It sounds like a major undertaking to me. If I succeed then I will have a major tool in my belt. Luckily the various databases look pretty similar so that once I figure out how to do it on one, the next 10 will be easier. John W. Colby Reality is what refuses to go away when you do not believe in it On 2/19/2014 9:55 AM, Arthur Fuller wrote: > John, > > There's nothing to it. Maria is a drop-in replacement for MySQL... with > several new features not yet implemented in MySQL. Initially I thought that > Maria would trail MySQL in terms of features, but not so. It's Oracle/MySQL > that's playying catch-up. > > Even if you opt for the paid support version, you still save a lot of money > compared with the SQL 2012 implementation. > > I haven't begun it yet, but I plan to add a new chapter on Maria to our > MySQL book and web site. > > Arthur > > On Wed, Feb 19, 2014 at 8:03 AM, John W Colby <jwcolby at gmail.com> wrote: > >> I would like to move my apps from SQL Server to MariaDb. The costs of >> licenses going forward make SQL Server 12 untenable for my clients.