[dba-SQLServer] Upgrade to MySql

Hans-Christian Andersen ha at phulse.com
Thu Aug 12 17:13:10 CDT 2010


Not that I'm promoting MySQL (I'd go PostgreSQL, if you want a solid
database with an enterprise feel to it for no cost), but the MySQL's InnoDB
engine does indeed support transactions. MySQL's MyISAM, on the other hand,
does not. But you can choose whatever you want your tables to be in.

MySQL is pretty stable and a faster database than most (certainly faster
than SQL Server on a bad day). Just don't expect it to perform any fancy DB
tricks for you without complications and it has little quirks here and
there.

I'd say the advantage over SQL Express is that MySQL is and always will be
free and therefore you do not get any imposed limitations to nudge you in
the direction of paying for a very costly license. From a cursory glance,
some limitations appear to be:

Limitations: SQL Server Express supports 1 physical processor, 1 GB memory,
> and 4 GB storage


> http://www.microsoft.com/sqlserver/2008/en/us/express.aspx


Ouch. That is a clear deal breaker for me.

Some more information:
http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx

My opinion is, stay away from SQL Express. It is simply a taster. There are
plenty of other alternatives that will suit you better. Did I already
mention PostgreSQL?


Hans-Christian
Web Application Development



On 12 August 2010 14:52, Jim Lawrence <jlawrenc1 at shaw.ca> wrote:

> There are a few good reasons for not going to MySQL.
>
> For example you can not roll back a transaction or series of transactions.
> For any application, that is at all like accounting, that is a big minus.
>
> Just because bound MDB applications get away with it does not mean that it
> is acceptable in the business world. Of course that is why a programmer
> uses
> ADO for data connection. (ADO has full BeginTrans, RollBack and Commit
> functionality but you must have the appropriately matching BE DB like MS
> SQL
> Express, PostgreSQL, Oracle Express Edition etc...)
>
> Jim
>
>
>
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mark
> Breen
> Sent: Thursday, August 12, 2010 4:34 AM
> To: Discussion concerning MS SQL Server
> Subject: Re: [dba-SQLServer] Upgrade to MySql
>
> Hello Rocky,
>
> What are the benefits to the client of mySQL over Microsoft SQL Express ?
>
> Thanks
>
> Mark
>
>
> On 8 August 2010 16:25, Rocky Smolin <rockysmolin at bchacc.com> wrote:
>
> >
> >  Dear List:
> >
> >  I have a client with a rather large application who is considering
> > upgrading  the back end to MySql.
> >
> >  Objects:
> >  ~100 forms
> >  ~150 queries
> >  ~75 reports
> >
> >  Lots of code modules with many lines and lots of CBF.
> >
> >  The app uses bound forms and lots of DAO.
> >
> >  BE is an mdb.  FE & BE are both A2K3.
> >
> >  Question is, of course, what is involved in converting this front end to
> > work with a MySQL back end?
> >
> >  MTIA,
> >
> >  Rocky Smolin
> >  Beach Access Software
> >  858-259-4334
> >  www.e-z-mrp.com ;
> >  www.bchacc.com ;
> >
> > _______________________________________________
> > dba-SQLServer mailing list
> > dba-SQLServer at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> > http://www.databaseadvisors.com
> >
> >
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>



More information about the dba-SQLServer mailing list