From rockysmolin at bchacc.com Sun Aug 8 10:25:32 2010 From: rockysmolin at bchacc.com (Rocky Smolin) Date: Sun, 8 Aug 2010 08:25:32 -0700 Subject: [dba-SQLServer] Upgrade to MySql Message-ID: 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 ; From accessd at shaw.ca Sun Aug 8 15:29:40 2010 From: accessd at shaw.ca (Jim Lawrence) Date: Sun, 8 Aug 2010 13:29:40 -0700 Subject: [dba-SQLServer] Upgrade to MySql In-Reply-To: References: Message-ID: <3A5AE6B63B50451A97893768B961AE0B@creativesystemdesigns.com> Hi Rocky: To say the least your work is cut out for you. A creditable job will/may cost the client a large whack of hours times your current prevailing rate. If they are OK with that assumption you can move to the next step. There are some commercial products that can assist with BE upgrade: http://www.navicat.com/en/products/navicat_mysql/mysql_overview.html http://www.navicat.com/en/buynow/store.html ...and dramatically reduce time and effort but... Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin Sent: Sunday, August 08, 2010 8:26 AM To: dba-SQLServer at databaseadvisors.com Subject: [dba-SQLServer] Upgrade to MySql 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 From stuart at lexacorp.com.pg Sun Aug 8 20:15:02 2010 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Mon, 09 Aug 2010 11:15:02 +1000 Subject: [dba-SQLServer] Upgrade to MySql In-Reply-To: References: Message-ID: <4C5F5696.30387.14604296@stuart.lexacorp.com.pg> If you are happy to go with ODBC linked tables, it's simple - just create a MySQL database with the same tables and link to them instead of the Access tables. It's quite possible that that is all you need. Try it and see whether there are perfomance problems - if so, you will need to look at optimising your data sets with views and pass- through queries. FWIW, I've used Access FEs with OBDC connections to SQL Server and/or MySQL in a number of cases and have not experienced any performance problems to date. -- Stuart On 8 Aug 2010 at 8:25, Rocky Smolin 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 > > From Gustav at cactus.dk Mon Aug 9 02:11:58 2010 From: Gustav at cactus.dk (Gustav Brock) Date: Mon, 09 Aug 2010 09:11:58 +0200 Subject: [dba-SQLServer] Upgrade to MySql Message-ID: Hi Rocky That is what I have seen as well. Free tools for converting your backend are available as well as several commercial like DeZign: http://www.datanamic.com/dezign/index.html /gustav >>> stuart at lexacorp.com.pg 09-08-2010 03:15 >>> If you are happy to go with ODBC linked tables, it's simple - just create a MySQL database with the same tables and link to them instead of the Access tables. It's quite possible that that is all you need. Try it and see whether there are perfomance problems - if so, you will need to look at optimising your data sets with views and pass- through queries. FWIW, I've used Access FEs with OBDC connections to SQL Server and/or MySQL in a number of cases and have not experienced any performance problems to date. -- Stuart On 8 Aug 2010 at 8:25, Rocky Smolin 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 ; From marklbreen at gmail.com Thu Aug 12 06:34:02 2010 From: marklbreen at gmail.com (Mark Breen) Date: Thu, 12 Aug 2010 12:34:02 +0100 Subject: [dba-SQLServer] Upgrade to MySql In-Reply-To: References: Message-ID: 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 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 > > From jlawrenc1 at shaw.ca Thu Aug 12 16:52:09 2010 From: jlawrenc1 at shaw.ca (Jim Lawrence) Date: Thu, 12 Aug 2010 14:52:09 -0700 Subject: [dba-SQLServer] Upgrade to MySql In-Reply-To: References: Message-ID: <40C3758DC39548049EAACB2CAC28ACF2@creativesystemdesigns.com> 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 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 From ha at phulse.com Thu Aug 12 17:13:10 2010 From: ha at phulse.com (Hans-Christian Andersen) Date: Thu, 12 Aug 2010 15:13:10 -0700 Subject: [dba-SQLServer] Upgrade to MySql In-Reply-To: <40C3758DC39548049EAACB2CAC28ACF2@creativesystemdesigns.com> References: <40C3758DC39548049EAACB2CAC28ACF2@creativesystemdesigns.com> Message-ID: 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 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 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 > > From df.waters at comcast.net Thu Aug 12 17:31:53 2010 From: df.waters at comcast.net (Dan Waters) Date: Thu, 12 Aug 2010 17:31:53 -0500 Subject: [dba-SQLServer] Upgrade to MySql In-Reply-To: References: <40C3758DC39548049EAACB2CAC28ACF2@creativesystemdesigns.com> Message-ID: SQL Server 2008 R2 Express supports 10 Gb of data storage: http://www.microsoft.com/sqlserver/2008/en/us/editions.aspx Dan -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Hans-Christian Andersen Sent: Thursday, August 12, 2010 5:13 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] Upgrade to MySql 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 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 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 > > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From stuart at lexacorp.com.pg Thu Aug 12 19:11:50 2010 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Fri, 13 Aug 2010 10:11:50 +1000 Subject: [dba-SQLServer] Upgrade to MySql In-Reply-To: <40C3758DC39548049EAACB2CAC28ACF2@creativesystemdesigns.com> References: , , <40C3758DC39548049EAACB2CAC28ACF2@creativesystemdesigns.com> Message-ID: <4C648DC6.21910.5084D4F@stuart.lexacorp.com.pg> On 12 Aug 2010 at 14:52, Jim Lawrence 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. http://dev.mysql.com/doc/refman/5.0/en/commit.html MySQL 5.0 Reference Manual :: 12 SQL Statement Syntax :: 12.3 MySQL Transactional and Locking Statements :: 12.3.1 START TRANSACTION, COMMIT, and ROLLBACK Syntax 12.3.1. START TRANSACTION, COMMIT, and ROLLBACK Syntax START TRANSACTION [WITH CONSISTENT SNAPSHOT] | BEGIN [WORK] COMMIT [WORK] [AND [NO] CHAIN] [[NO] RELEASE] ROLLBACK [WORK] [AND [NO] CHAIN] [[NO] RELEASE] SET autocommit = {0 | 1} The START TRANSACTION or BEGIN statement begins a new transaction. COMMIT commits the current transaction, making its changes permanent. ROLLBACK rolls back the current transaction, canceling its changes. The SET autocommit statement disables or enables the default autocommit mode for the current session. Beginning with MySQL 5.0.3, the optional WORK keyword is supported for COMMIT and ROLLBACK, as are the CHAIN and RELEASE clauses. CHAIN and RELEASE can be used for additional control over transaction completion. The value of the completion_type system variable determines the default completion behavior. From accessd at shaw.ca Thu Aug 12 20:47:11 2010 From: accessd at shaw.ca (Jim Lawrence) Date: Thu, 12 Aug 2010 18:47:11 -0700 Subject: [dba-SQLServer] Upgrade to MySql In-Reply-To: <4C648DC6.21910.5084D4F@stuart.lexacorp.com.pg> References: <40C3758DC39548049EAACB2CAC28ACF2@creativesystemdesigns.com> <4C648DC6.21910.5084D4F@stuart.lexacorp.com.pg> Message-ID: <3A566FF1C15D4788A11E4DC5F5D0521C@creativesystemdesigns.com> Hi Stuart: That is correct Stuart but check out Han's post on the subject. The question is can the rollback be done via connection calls from ADO-OLE. Are the following comments written by a MySQL programmer correct or just dated? http://www.draconianoverlord.com/2010/07/22/dammit-mysql.html Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Thursday, August 12, 2010 5:12 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] Upgrade to MySql On 12 Aug 2010 at 14:52, Jim Lawrence 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. http://dev.mysql.com/doc/refman/5.0/en/commit.html MySQL 5.0 Reference Manual :: 12 SQL Statement Syntax :: 12.3 MySQL Transactional and Locking Statements :: 12.3.1 START TRANSACTION, COMMIT, and ROLLBACK Syntax 12.3.1. START TRANSACTION, COMMIT, and ROLLBACK Syntax START TRANSACTION [WITH CONSISTENT SNAPSHOT] | BEGIN [WORK] COMMIT [WORK] [AND [NO] CHAIN] [[NO] RELEASE] ROLLBACK [WORK] [AND [NO] CHAIN] [[NO] RELEASE] SET autocommit = {0 | 1} The START TRANSACTION or BEGIN statement begins a new transaction. COMMIT commits the current transaction, making its changes permanent. ROLLBACK rolls back the current transaction, canceling its changes. The SET autocommit statement disables or enables the default autocommit mode for the current session. Beginning with MySQL 5.0.3, the optional WORK keyword is supported for COMMIT and ROLLBACK, as are the CHAIN and RELEASE clauses. CHAIN and RELEASE can be used for additional control over transaction completion. The value of the completion_type system variable determines the default completion behavior. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com