Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Works for me. -- WSS4CF - WS-Security framework for CF http://wss4cf.riaforge.org/ On 11 May 2011 11:26, Dave Watts dwa...@figleaf.com wrote: You could always both swap to a real database: http://www.oracle.com/technetwork/database/express-edition/overview/index.html Your DB2 link is broken. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344439 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
No. Not all DB's are equal just because they all run SQL. -- WSS4CF - WS-Security framework for CF http://wss4cf.riaforge.org/ On 11 May 2011 10:45, Maureen mamamaur...@gmail.com wrote: They are all real databases. The majority of the problems that website databases have are caused by badly written code, inefficient queries and poor performance tuning, and have nothing to do with the database platfor ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:30 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Funnily enough I looked into Oracle Express recently for a client, and it is not actually suitable for web apps. It is primarily intended for mobile platforms or portable media. On Wed, May 11, 2011 at 8:58 AM, James Holmes james.hol...@gmail.comwrote: No. Not all DB's are equal just because they all run SQL. -- WSS4CF - WS-Security framework for CF http://wss4cf.riaforge.org/ On 11 May 2011 10:45, Maureen mamamaur...@gmail.com wrote: They are all real databases. The majority of the problems that website databases have are caused by badly written code, inefficient queries and poor performance tuning, and have nothing to do with the database platfor ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:31 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
RE: Migrating a DB from MS SQL 2000 into MySQL latest release
Will, I pinched some of Gerald's popcorn and had a good read, thanks for all the replies. It has been very interesting reading the discussion on the various DB's. Overall, SQL Server Express is coming out on top for me. My existing databases don't get anywhere near the 10GB limit, and I wouldn't have any issues transfering my existing code straight across, apart from one issue. I read that SQL 2008 Express does not include DTS/SSIS, can anyone confirm that please? Are there any other limitations / pitfalls of using SQL 2008 Express? I'm also wondering if there is much of a learning curve, not so much as for new features in 2008, but just in supporting my existing databases? I will need to run SQL 2008 Express alongside SQL 2000 on the same server while I port everything across. Any issues I might encounter? Many thanks, Jenny Gavin-Wear Fast Track Online Tel: 01262 602013 http://www.fasttrackonline.co.uk/ No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3629 - Release Date: 05/10/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:39 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Here is a complete feature matrix. http://msdn.microsoft.com/en-us/library/cc645993.aspx I'm sure I used SSIS with 2005 Express, so I would expect it is with 2008. You certainly have import/export services anyway. Just make sure you get SQL Server Express with Tools. If you find features missing from the Management Studio express, there is a little cheat, you can download the FULL EDITION trial of SQL Server 2008 with tools, and get the full edition of Management Studio, which i'm pretty sure never expires, at least it didn't with 2005. The learning curve will be with using the new Management Studio rather than Enterprise manager, although I believe you can still use enterprise manager up to a point. Other than that your database will work the same unless you choose to learn and implement and of the new features. 2008 is miles apart from 2000. On Wed, May 11, 2011 at 3:52 PM, Jenny Gavin-Wear jenn...@fasttrackonline.co.uk wrote: Will, I pinched some of Gerald's popcorn and had a good read, thanks for all the replies. It has been very interesting reading the discussion on the various DB's. Overall, SQL Server Express is coming out on top for me. My existing databases don't get anywhere near the 10GB limit, and I wouldn't have any issues transfering my existing code straight across, apart from one issue. I read that SQL 2008 Express does not include DTS/SSIS, can anyone confirm that please? Are there any other limitations / pitfalls of using SQL 2008 Express? I'm also wondering if there is much of a learning curve, not so much as for new features in 2008, but just in supporting my existing databases? I will need to run SQL 2008 Express alongside SQL 2000 on the same server while I port everything across. Any issues I might encounter? Many thanks, Jenny Gavin-Wear Fast Track Online Tel: 01262 602013 http://www.fasttrackonline.co.uk/ No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3629 - Release Date: 05/10/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344451 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
lol. ;-) On 5/10/2011 8:26 PM, Dave Watts wrote: You could always both swap to a real database: http://www.oracle.com/technetwork/database/express-edition/overview/index.html Your DB2 link is broken. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344461 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
I second the comment on Navicat. It's intuitive and easy to use and the new Premium edition supports MS-SQL as well as MySQL, Postgre, Oracle and SQLite. And no, I don't have any affiliation with them, I just love their product :-) I've converted several databases from MS-SQL to MySQL with no problems whatsoever. I now use Navicat exclusively to manage all of my client databases and I haven't even had to install the dreaded SQL Enterprise Manager on my new system (which makes me extremely happy because I can't stand Enterprise Manager). For backups or transferring to a new server, I think Navicat is MUCH easier and more intuitive than Microsoft's built-in tools. Even moving a database from one MS-SQL Server to another is just a couple of clicks of the mouse. With regards to the comment about the type of backup, I actually just schedule a nightly sync from my Production DB to a dedicated backup version on the Staging Server (or Development Server for clients that don't have a staging environment). This way, we actually have a LIVE fail over we can bring online almost immediately, while we repair or replace the Production server. I realize that might not be an option for all situations (especially really large DBs), but it's worked extremely well for me over the years. I've never seen a MySQL database get corrupted and I've worked with hundreds of them (though granted most of them were fairly small). Just my 2 cents worth. -Mike I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344462 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
While installing the trial of SQL Server 2008 will get you the full Management Studio and Business Development Studio (or whatever it is called in 2008, and is required for developing SSIS solutions), SQL Server Express does not have the SSIS service. You have to have at least one full SQL Server 2008 server somewhere to have an SSIS service. You might consider purchasing SQL Server 2008 Developer Edition (which should be about $50) which is essentially a fully functioning version of SQL Server 2008 Enterprise with the licensing restriction that it only be used for development and not production. Link to Developer Edition on MicrosoftStore.com: http://www.microsoftstore.com/store/msstore/en_US/pd/productID.221634300/search.true HTH, Carl On 5/11/2011 8:08 AM, Russ Michaels wrote: I'm sure I used SSIS with 2005 Express, so I would expect it is with 2008. You certainly have import/export services anyway. Just make sure you get SQL Server Express with Tools. If you find features missing from the Management Studio express, there is a little cheat, you can download the FULL EDITION trial of SQL Server 2008 with tools, and get the full edition of Management Studio, which i'm pretty sure never expires, at least it didn't with 2005. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344464 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
FWIW, here's some code for automating the backup process in SQL Server Express: http://www.cfgears.com/index.cfm/2010/7/20/Automating-backups-for-SQL-Server-Express Thanks, Eric Cobb http://www.cfgears.com Help me make a difference this summer -http://bit.ly/i8dJvQ On 5/11/2011 1:36 PM, Carl Von Stetten wrote: While installing the trial of SQL Server 2008 will get you the full Management Studio and Business Development Studio (or whatever it is called in 2008, and is required for developing SSIS solutions), SQL Server Express does not have the SSIS service. You have to have at least one full SQL Server 2008 server somewhere to have an SSIS service. You might consider purchasing SQL Server 2008 Developer Edition (which should be about $50) which is essentially a fully functioning version of SQL Server 2008 Enterprise with the licensing restriction that it only be used for development and not production. Link to Developer Edition on MicrosoftStore.com: http://www.microsoftstore.com/store/msstore/en_US/pd/productID.221634300/search.true HTH, Carl On 5/11/2011 8:08 AM, Russ Michaels wrote: I'm sure I used SSIS with 2005 Express, so I would expect it is with 2008. You certainly have import/export services anyway. Just make sure you get SQL Server Express with Tools. If you find features missing from the Management Studio express, there is a little cheat, you can download the FULL EDITION trial of SQL Server 2008 with tools, and get the full edition of Management Studio, which i'm pretty sure never expires, at least it didn't with 2005. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344465 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
RE: Migrating a DB from MS SQL 2000 into MySQL latest release
Thanks for the info on Navicat, it looks really great, but I'm going to stick with SQL Express for now. Installing/testing SQL 2008 Express went extremely well. I'll need to get my head around the changes in FULLTEXT. If anyone else is looking at Express, I've blogged the installation notes:- http://fasttrackonline.blogspot.com/2011/05/coldfusion-and-microsot-sql-expr ess-r2.html Enjoy! Jenny Gavin-Wear Fast Track Online Tel: 01262 602013 http://www.fasttrackonline.co.uk/ -Original Message- From: M P [mailto:miketot...@gmail.com] Sent: 11 May 2011 19:48 To: cf-talk Subject: Re: Migrating a DB from MS SQL 2000 into MySQL latest release I second the comment on Navicat. It's intuitive and easy to use and the new Premium edition supports MS-SQL as well as MySQL, Postgre, Oracle and SQLite. And no, I don't have any affiliation with them, I just love their product :-) I've converted several databases from MS-SQL to MySQL with no problems whatsoever. I now use Navicat exclusively to manage all of my client databases and I haven't even had to install the dreaded SQL Enterprise Manager on my new system (which makes me extremely happy because I can't stand Enterprise Manager). For backups or transferring to a new server, I think Navicat is MUCH easier and more intuitive than Microsoft's built-in tools. Even moving a database from one MS-SQL Server to another is just a couple of clicks of the mouse. With regards to the comment about the type of backup, I actually just schedule a nightly sync from my Production DB to a dedicated backup version on the Staging Server (or Development Server for clients that don't have a staging environment). This way, we actually have a LIVE fail over we can bring online almost immediately, while we repair or replace the Production server. I realize that might not be an option for all situations (especially really large DBs), but it's worked extremely well for me over the years. I've never seen a MySQL database get corrupted and I've worked with hundreds of them (though granted most of them were fairly small). Just my 2 cents worth. -Mike I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344467 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Judah, Yes it is nice to have power, but it is rather like buying a Porshe to drive around town at 30MPH, sure you can brag about it and tell everyone how you could drive at 200mph if you wanted to, but really you are never going to do it, and a more practical car is really going to do a better job for you in that scenario. My comments are based on my own *REAL WORLD* experience hosting hundreds of databases over many years, rather than as a developer building a single database/website. but in those years I have experienced the following, which is why I will always prefer/recommend MSSQL. MySQL databases corrupt quite easily and need to be repaired (even on dedicated machines) Never had a MSSQL corruption problem since MSSQL 2000 MySQL will easily get overloaded by a single database and consume 100% CPU requiring a restart, only experienced this on v4 so far though. Never had that problem on MSSQL MySQL is a PITA to backup and restore, time consuming and quirky and dumps not always reliable. MSSQL is simple and quick to backup/restore/migrate. Our MSSQL servers are able to host far more databases than the MySQL servers. Now granted the limits on Express edition would mean you could not host HUGE memory/CPU hogging databases, but as I said, this scenario is quite rare, most people's databases do not come anywhere near this and the Express edition will handle them just fine, so it certainly is not just good for development. We ran SQL 2005 express for years in a shared hosting environment with no problems at all, the limits did not cause any problems for a long time. We managed to get a lot of databases on the server until it started to run out of power, and now we use SQL Server 2008 web edition, which is actually very cheap to run. Again I would point out that if you are in the need of great power and reliability, then you should be running your own server and probably not running the free editions anyway. The problem with databases and database servers is that most developers really don;t know much about them, and will just throw together a basic database and rely on the servers out of the box config. In this area MSSQL shines, as you can install it out of the box with no tweaking and it will run like a dream. With MySQL on the other hand you really need a deeper understanding of how it works to be able to fine tune its performance and you also need to understand the different database engines it utilises and when to use them, again something most people do not do, which adds to the reliability/performance issues with databases. To be honest this is somewhat of a rarity as M$ products are usually not known for being the best, often it is the 3rd party products which are superior, but you also have to remember that M$ did not originally create SQL Server, it was originally Sybase. So if you are in the anti-Microsoft camp you may find this history of SQL server interesting. http://insidesqlserver.com/companion/History%20of%20SQL%20Server.pdf At the end of the day this is just my opinion/experience, you do not have to agree with it. On Tue, May 10, 2011 at 4:18 AM, Judah McAuley ju...@wiredotter.com wrote: MySql is free though licensing is a bit complicated because of a dual-license model. The community edition includes many enterprise sorts of features like replication and partitioning. If I recall, there are additional backup tools and monitoring in the paid enterprise edition. If you want to go completely free from the weird Oracle ownership stuff (which I think is wise, personally), there is the MariaDB fork which is entirely FOSS as far as I know. What enterprise features are you thinking aren't in the community edition? MySql community edition has none of the limitations present in MS SQL Express edition. Honestly, not taking advantage of more than a gig of RAM or 1 cpu core is just stupid. Why would you even have a database server? I suppose if you are housing the db on the same machine as your app server then...well, you have plenty of other problems at that point. Sql Express is great for development (though I prefer developer edition myself). It is not meant for production websites, period. That's why Microsoft has a Web edition. I like SQL Server and use it but it is wrong to try and compare Sql Express and MySql community edition, they are completely different classes of software. That being said, I still think people should check out PostGres. A feature set comparable to Oracle/MS SQL/Sybase and genuinely FOSS, unlike MySql. Tasty DB goodness. Cheers, Judah On Mon, May 9, 2011 at 4:57 PM, Russ Michaels r...@michaels.me.uk wrote: Many people often wrongly assume that MySQL is simply FREE, which is not correct. Many people are also completely unaware that there is a FREE MSSQL Express edition. The FREE version is the community edition, which also has limitations, look them up, If you want enterprise features then you have to pay i'm
RE: Migrating a DB from MS SQL 2000 into MySQL latest release
I've been using MySQL for over 10 years and never had any problems with it. Get PremiumSoft's Navicat for your GUI and management is a breeze. Never had anything corrupted and MySQL only overloads the CPU when code is not working correctly. Backups can easily be automated with Navicat, as well. I've had good experience with it and highly recommend it. Rick -Original Message- From: Russ Michaels [mailto:r...@michaels.me.uk] Sent: Tuesday, May 10, 2011 7:14 AM To: cf-talk Subject: Re: Migrating a DB from MS SQL 2000 into MySQL latest release Judah, Yes it is nice to have power, but it is rather like buying a Porshe to drive around town at 30MPH, sure you can brag about it and tell everyone how you could drive at 200mph if you wanted to, but really you are never going to do it, and a more practical car is really going to do a better job for you in that scenario. My comments are based on my own *REAL WORLD* experience hosting hundreds of databases over many years, rather than as a developer building a single database/website. but in those years I have experienced the following, which is why I will always prefer/recommend MSSQL. MySQL databases corrupt quite easily and need to be repaired (even on dedicated machines) Never had a MSSQL corruption problem since MSSQL 2000 MySQL will easily get overloaded by a single database and consume 100% CPU requiring a restart, only experienced this on v4 so far though. Never had that problem on MSSQL MySQL is a PITA to backup and restore, time consuming and quirky and dumps not always reliable. MSSQL is simple and quick to backup/restore/migrate. Our MSSQL servers are able to host far more databases than the MySQL servers. Now granted the limits on Express edition would mean you could not host HUGE memory/CPU hogging databases, but as I said, this scenario is quite rare, most people's databases do not come anywhere near this and the Express edition will handle them just fine, so it certainly is not just good for development. We ran SQL 2005 express for years in a shared hosting environment with no problems at all, the limits did not cause any problems for a long time. We managed to get a lot of databases on the server until it started to run out of power, and now we use SQL Server 2008 web edition, which is actually very cheap to run. Again I would point out that if you are in the need of great power and reliability, then you should be running your own server and probably not running the free editions anyway. The problem with databases and database servers is that most developers really don;t know much about them, and will just throw together a basic database and rely on the servers out of the box config. In this area MSSQL shines, as you can install it out of the box with no tweaking and it will run like a dream. With MySQL on the other hand you really need a deeper understanding of how it works to be able to fine tune its performance and you also need to understand the different database engines it utilises and when to use them, again something most people do not do, which adds to the reliability/performance issues with databases. To be honest this is somewhat of a rarity as M$ products are usually not known for being the best, often it is the 3rd party products which are superior, but you also have to remember that M$ did not originally create SQL Server, it was originally Sybase. So if you are in the anti-Microsoft camp you may find this history of SQL server interesting. http://insidesqlserver.com/companion/History%20of%20SQL%20Server.pdf At the end of the day this is just my opinion/experience, you do not have to agree with it. On Tue, May 10, 2011 at 4:18 AM, Judah McAuley ju...@wiredotter.com wrote: MySql is free though licensing is a bit complicated because of a dual-license model. The community edition includes many enterprise sorts of features like replication and partitioning. If I recall, there are additional backup tools and monitoring in the paid enterprise edition. If you want to go completely free from the weird Oracle ownership stuff (which I think is wise, personally), there is the MariaDB fork which is entirely FOSS as far as I know. What enterprise features are you thinking aren't in the community edition? MySql community edition has none of the limitations present in MS SQL Express edition. Honestly, not taking advantage of more than a gig of RAM or 1 cpu core is just stupid. Why would you even have a database server? I suppose if you are housing the db on the same machine as your app server then...well, you have plenty of other problems at that point. Sql Express is great for development (though I prefer developer edition myself). It is not meant for production websites, period. That's why Microsoft has a Web edition. I like SQL Server and use it but it is wrong to try and compare Sql Express and MySql community edition, they are completely different classes of software. That being said, I still
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
I'm glad your experiences have been good Rich. Perhaps you can quantify the scale, i.e how many databases over how long, i'm sure it will be more helpful to present a bigger picture. But do remember just as a car owner can say my car has been great, this cannot be applied to every single owner of that same car. You have to consider others experiences as well. Of course not everyone has the same problems, but if hundreds of others have had the same problems, then you cannot really ignore it. As I said, my experience is with hundreds of customers/databases over many years, so it is not really just my own opinion/experience, but all the experience of all those other customers as well, I am more of a messenger really. The common problems and issues can be googled, like this for example. http://www.google.co.uk/search?q=mysql+corrupted+tablesie=utf-8oe=utf-8aq=trls=org.mozilla:en-GB:officialclient=firefox-a You are correct that backups can be automated, they can even be automated with the FREE MySQLAdministrator that used to come free with mysql, but for some bizarre reason Oracle removed this feature from the new workbench. However the problem is in the way that backups work, it is not really a backup, it is a DUMP from the database as one huge SQL script to drop tables, re-create tables and re-insert data. This causes some of the following issues on shared hosting particularly 1. many people only have access to PHPMyadmin, and the DUMP can often be very large even for a moderate sized databases, doing large dumps simply wont work most of the time with PHPMyadmin, whether your backing up or restoring, it just times out or cannot cope. Often the only solution is command line directly on the server. 2. if moving between versions importing the dump wont work sometimes and it can be a PITA to figure out why, especially if it is a BIG database and you have to keep re-exporting it. The CPU overload can of course be blamed on poor code, more usually bad SQL, but this problem exists on every platform in every language, but MSSQL does seem to cope with bad queries much better. HTH On Tue, May 10, 2011 at 1:42 PM, Rick Faircloth r...@whitestonemedia.comwrote: I've been using MySQL for over 10 years and never had any problems with it. Get PremiumSoft's Navicat for your GUI and management is a breeze. Never had anything corrupted and MySQL only overloads the CPU when code is not working correctly. Backups can easily be automated with Navicat, as well. I've had good experience with it and highly recommend it. Rick -Original Message- From: Russ Michaels [mailto:r...@michaels.me.uk] Sent: Tuesday, May 10, 2011 7:14 AM To: cf-talk Subject: Re: Migrating a DB from MS SQL 2000 into MySQL latest release Judah, Yes it is nice to have power, but it is rather like buying a Porshe to drive around town at 30MPH, sure you can brag about it and tell everyone how you could drive at 200mph if you wanted to, but really you are never going to do it, and a more practical car is really going to do a better job for you in that scenario. My comments are based on my own *REAL WORLD* experience hosting hundreds of databases over many years, rather than as a developer building a single database/website. but in those years I have experienced the following, which is why I will always prefer/recommend MSSQL. MySQL databases corrupt quite easily and need to be repaired (even on dedicated machines) Never had a MSSQL corruption problem since MSSQL 2000 MySQL will easily get overloaded by a single database and consume 100% CPU requiring a restart, only experienced this on v4 so far though. Never had that problem on MSSQL MySQL is a PITA to backup and restore, time consuming and quirky and dumps not always reliable. MSSQL is simple and quick to backup/restore/migrate. Our MSSQL servers are able to host far more databases than the MySQL servers. Now granted the limits on Express edition would mean you could not host HUGE memory/CPU hogging databases, but as I said, this scenario is quite rare, most people's databases do not come anywhere near this and the Express edition will handle them just fine, so it certainly is not just good for development. We ran SQL 2005 express for years in a shared hosting environment with no problems at all, the limits did not cause any problems for a long time. We managed to get a lot of databases on the server until it started to run out of power, and now we use SQL Server 2008 web edition, which is actually very cheap to run. Again I would point out that if you are in the need of great power and reliability, then you should be running your own server and probably not running the free editions anyway. The problem with databases and database servers is that most developers really don;t know much about them, and will just throw together a basic database and rely on the servers out of the box config. In this area MSSQL shines, as you can
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Or like this: http://www.google.com.au/search?sourceid=chromeie=UTF-8q=ms+sql+express+corrupt+tables -- WSS4CF - WS-Security framework for CF http://wss4cf.riaforge.org/ On 10 May 2011 22:31, Russ Michaels r...@michaels.me.uk wrote: The common problems and issues can be googled, like this for example. http://www.google.co.uk/search?q=mysql+corrupted+tablesie=utf-8oe=utf-8aq=trls=org.mozilla:en-GB:officialclient=firefox-a ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344404 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Yes James, well done :-) On Tue, May 10, 2011 at 3:37 PM, James Holmes james.hol...@gmail.comwrote: Or like this: http://www.google.com.au/search?sourceid=chromeie=UTF-8q=ms+sql+express+corrupt+tables -- WSS4CF - WS-Security framework for CF http://wss4cf.riaforge.org/ On 10 May 2011 22:31, Russ Michaels r...@michaels.me.uk wrote: The common problems and issues can be googled, like this for example. http://www.google.co.uk/search?q=mysql+corrupted+tablesie=utf-8oe=utf-8aq=trls=org.mozilla:en-GB:officialclient=firefox-a ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344406 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
RE: Migrating a DB from MS SQL 2000 into MySQL latest release
My experience has mostly been with relatively small databases running anywhere from 2 months to 8 years. The most trafficked site I host serves about 50,000 pages views per month with almost all pages serving some database-driven dynamic content. I usually have about 25 databases running simultaneously on the same server with my sites. I don't have a lot of complex code (at least not to me) running on these servers accessing the database, so that cuts down on coding problems that might cause MySQL to spike the CPU. I did have more issues with that a few years ago, and even once recently on the server, but the CPU spiking has always been related to coding or another piece of software trying to run cfexecute operations, etc. I've never tracked an issue back to a problem with MySQL. And, I realize that every user's experience is going to be different, just as every car driver's accident experience is different with the same make and model, due mostly to the driver's use and driving capability. Some folks just have a propensity for crashing. :o) I have no complaints with MySQL for my requirements. It's been good to me. I've always been a Windows Server user, fyi... Rick -Original Message- From: Russ Michaels [mailto:r...@michaels.me.uk] Sent: Tuesday, May 10, 2011 10:31 AM To: cf-talk Subject: Re: Migrating a DB from MS SQL 2000 into MySQL latest release I'm glad your experiences have been good Rich. Perhaps you can quantify the scale, i.e how many databases over how long, i'm sure it will be more helpful to present a bigger picture. But do remember just as a car owner can say my car has been great, this cannot be applied to every single owner of that same car. You have to consider others experiences as well. Of course not everyone has the same problems, but if hundreds of others have had the same problems, then you cannot really ignore it. As I said, my experience is with hundreds of customers/databases over many years, so it is not really just my own opinion/experience, but all the experience of all those other customers as well, I am more of a messenger really. The common problems and issues can be googled, like this for example. http://www.google.co.uk/search?q=mysql+corrupted+tablesie=utf-8oe=utf-8aq =trls=org.mozilla:en-GB:officialclient=firefox-a You are correct that backups can be automated, they can even be automated with the FREE MySQLAdministrator that used to come free with mysql, but for some bizarre reason Oracle removed this feature from the new workbench. However the problem is in the way that backups work, it is not really a backup, it is a DUMP from the database as one huge SQL script to drop tables, re-create tables and re-insert data. This causes some of the following issues on shared hosting particularly 1. many people only have access to PHPMyadmin, and the DUMP can often be very large even for a moderate sized databases, doing large dumps simply wont work most of the time with PHPMyadmin, whether your backing up or restoring, it just times out or cannot cope. Often the only solution is command line directly on the server. 2. if moving between versions importing the dump wont work sometimes and it can be a PITA to figure out why, especially if it is a BIG database and you have to keep re-exporting it. The CPU overload can of course be blamed on poor code, more usually bad SQL, but this problem exists on every platform in every language, but MSSQL does seem to cope with bad queries much better. HTH On Tue, May 10, 2011 at 1:42 PM, Rick Faircloth r...@whitestonemedia.comwrote: I've been using MySQL for over 10 years and never had any problems with it. Get PremiumSoft's Navicat for your GUI and management is a breeze. Never had anything corrupted and MySQL only overloads the CPU when code is not working correctly. Backups can easily be automated with Navicat, as well. I've had good experience with it and highly recommend it. Rick -Original Message- From: Russ Michaels [mailto:r...@michaels.me.uk] Sent: Tuesday, May 10, 2011 7:14 AM To: cf-talk Subject: Re: Migrating a DB from MS SQL 2000 into MySQL latest release Judah, Yes it is nice to have power, but it is rather like buying a Porshe to drive around town at 30MPH, sure you can brag about it and tell everyone how you could drive at 200mph if you wanted to, but really you are never going to do it, and a more practical car is really going to do a better job for you in that scenario. My comments are based on my own *REAL WORLD* experience hosting hundreds of databases over many years, rather than as a developer building a single database/website. but in those years I have experienced the following, which is why I will always prefer/recommend MSSQL. MySQL databases corrupt quite easily and need to be repaired (even on dedicated machines) Never had a MSSQL corruption problem since MSSQL 2000 MySQL will easily get overloaded by a single database and consume 100% CPU
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Presumably all those databases were designed by you and all the code written by you, so the lack of issues hopefully means all your code was good :-) On Tue, May 10, 2011 at 4:45 PM, Rick Faircloth r...@whitestonemedia.comwrote: My experience has mostly been with relatively small databases running anywhere from 2 months to 8 years. The most trafficked site I host serves about 50,000 pages views per month with almost all pages serving some database-driven dynamic content. I usually have about 25 databases running simultaneously on the same server with my sites. I don't have a lot of complex code (at least not to me) running on these servers accessing the database, so that cuts down on coding problems that might cause MySQL to spike the CPU. I did have more issues with that a few years ago, and even once recently on the server, but the CPU spiking has always been related to coding or another piece of software trying to run cfexecute operations, etc. I've never tracked an issue back to a problem with MySQL. And, I realize that every user's experience is going to be different, just as every car driver's accident experience is different with the same make and model, due mostly to the driver's use and driving capability. Some folks just have a propensity for crashing. :o) I have no complaints with MySQL for my requirements. It's been good to me. I've always been a Windows Server user, fyi... Rick -Original Message- From: Russ Michaels [mailto:r...@michaels.me.uk] Sent: Tuesday, May 10, 2011 10:31 AM To: cf-talk Subject: Re: Migrating a DB from MS SQL 2000 into MySQL latest release I'm glad your experiences have been good Rich. Perhaps you can quantify the scale, i.e how many databases over how long, i'm sure it will be more helpful to present a bigger picture. But do remember just as a car owner can say my car has been great, this cannot be applied to every single owner of that same car. You have to consider others experiences as well. Of course not everyone has the same problems, but if hundreds of others have had the same problems, then you cannot really ignore it. As I said, my experience is with hundreds of customers/databases over many years, so it is not really just my own opinion/experience, but all the experience of all those other customers as well, I am more of a messenger really. The common problems and issues can be googled, like this for example. http://www.google.co.uk/search?q=mysql+corrupted+tablesie=utf-8oe=utf-8aq =trls=org.mozilla:en-GB:officialclient=firefox-ahttp://www.google.co.uk/search?q=mysql+corrupted+tablesie=utf-8oe=utf-8aq%0A=trls=org.mozilla:en-GB:officialclient=firefox-a You are correct that backups can be automated, they can even be automated with the FREE MySQLAdministrator that used to come free with mysql, but for some bizarre reason Oracle removed this feature from the new workbench. However the problem is in the way that backups work, it is not really a backup, it is a DUMP from the database as one huge SQL script to drop tables, re-create tables and re-insert data. This causes some of the following issues on shared hosting particularly 1. many people only have access to PHPMyadmin, and the DUMP can often be very large even for a moderate sized databases, doing large dumps simply wont work most of the time with PHPMyadmin, whether your backing up or restoring, it just times out or cannot cope. Often the only solution is command line directly on the server. 2. if moving between versions importing the dump wont work sometimes and it can be a PITA to figure out why, especially if it is a BIG database and you have to keep re-exporting it. The CPU overload can of course be blamed on poor code, more usually bad SQL, but this problem exists on every platform in every language, but MSSQL does seem to cope with bad queries much better. HTH On Tue, May 10, 2011 at 1:42 PM, Rick Faircloth r...@whitestonemedia.comwrote: I've been using MySQL for over 10 years and never had any problems with it. Get PremiumSoft's Navicat for your GUI and management is a breeze. Never had anything corrupted and MySQL only overloads the CPU when code is not working correctly. Backups can easily be automated with Navicat, as well. I've had good experience with it and highly recommend it. Rick -Original Message- From: Russ Michaels [mailto:r...@michaels.me.uk] Sent: Tuesday, May 10, 2011 7:14 AM To: cf-talk Subject: Re: Migrating a DB from MS SQL 2000 into MySQL latest release Judah, Yes it is nice to have power, but it is rather like buying a Porshe to drive around town at 30MPH, sure you can brag about it and tell everyone how you could drive at 200mph if you wanted to, but really you are never going to do it, and a more practical car is really going to do a better job for you in that scenario. My comments are based on my own *REAL WORLD
RE: Migrating a DB from MS SQL 2000 into MySQL latest release
All true... now as far as all your code was good... I don't know about that, but it gets the job done. :o) -Original Message- From: Russ Michaels [mailto:r...@michaels.me.uk] Sent: Tuesday, May 10, 2011 12:26 PM To: cf-talk Subject: Re: Migrating a DB from MS SQL 2000 into MySQL latest release Presumably all those databases were designed by you and all the code written by you, so the lack of issues hopefully means all your code was good :-) On Tue, May 10, 2011 at 4:45 PM, Rick Faircloth r...@whitestonemedia.comwrote: My experience has mostly been with relatively small databases running anywhere from 2 months to 8 years. The most trafficked site I host serves about 50,000 pages views per month with almost all pages serving some database-driven dynamic content. I usually have about 25 databases running simultaneously on the same server with my sites. I don't have a lot of complex code (at least not to me) running on these servers accessing the database, so that cuts down on coding problems that might cause MySQL to spike the CPU. I did have more issues with that a few years ago, and even once recently on the server, but the CPU spiking has always been related to coding or another piece of software trying to run cfexecute operations, etc. I've never tracked an issue back to a problem with MySQL. And, I realize that every user's experience is going to be different, just as every car driver's accident experience is different with the same make and model, due mostly to the driver's use and driving capability. Some folks just have a propensity for crashing. :o) I have no complaints with MySQL for my requirements. It's been good to me. I've always been a Windows Server user, fyi... Rick -Original Message- From: Russ Michaels [mailto:r...@michaels.me.uk] Sent: Tuesday, May 10, 2011 10:31 AM To: cf-talk Subject: Re: Migrating a DB from MS SQL 2000 into MySQL latest release I'm glad your experiences have been good Rich. Perhaps you can quantify the scale, i.e how many databases over how long, i'm sure it will be more helpful to present a bigger picture. But do remember just as a car owner can say my car has been great, this cannot be applied to every single owner of that same car. You have to consider others experiences as well. Of course not everyone has the same problems, but if hundreds of others have had the same problems, then you cannot really ignore it. As I said, my experience is with hundreds of customers/databases over many years, so it is not really just my own opinion/experience, but all the experience of all those other customers as well, I am more of a messenger really. The common problems and issues can be googled, like this for example. http://www.google.co.uk/search?q=mysql+corrupted+tablesie=utf-8oe=utf-8aq =trls=org.mozilla:en-GB:officialclient=firefox-ahttp://www.google.co.uk/s earch?q=mysql+corrupted+tablesie=utf-8oe=utf-8aq%0A=trls=org.mozilla:en- GB:officialclient=firefox-a You are correct that backups can be automated, they can even be automated with the FREE MySQLAdministrator that used to come free with mysql, but for some bizarre reason Oracle removed this feature from the new workbench. However the problem is in the way that backups work, it is not really a backup, it is a DUMP from the database as one huge SQL script to drop tables, re-create tables and re-insert data. This causes some of the following issues on shared hosting particularly 1. many people only have access to PHPMyadmin, and the DUMP can often be very large even for a moderate sized databases, doing large dumps simply wont work most of the time with PHPMyadmin, whether your backing up or restoring, it just times out or cannot cope. Often the only solution is command line directly on the server. 2. if moving between versions importing the dump wont work sometimes and it can be a PITA to figure out why, especially if it is a BIG database and you have to keep re-exporting it. The CPU overload can of course be blamed on poor code, more usually bad SQL, but this problem exists on every platform in every language, but MSSQL does seem to cope with bad queries much better. HTH On Tue, May 10, 2011 at 1:42 PM, Rick Faircloth r...@whitestonemedia.comwrote: I've been using MySQL for over 10 years and never had any problems with it. Get PremiumSoft's Navicat for your GUI and management is a breeze. Never had anything corrupted and MySQL only overloads the CPU when code is not working correctly. Backups can easily be automated with Navicat, as well. I've had good experience with it and highly recommend it. Rick -Original Message- From: Russ Michaels [mailto:r...@michaels.me.uk] Sent: Tuesday, May 10, 2011 7:14 AM To: cf-talk Subject: Re: Migrating a DB from MS SQL 2000 into MySQL latest release Judah, Yes it is nice to have power, but it is rather like buying a Porshe
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Re: good code: I've done this once (and am about to do it again) so I'll share a few bits that I learned re: code changes: 99% of my code was fine. But I had to adjust some syntax. MSSQL vs MySQL: LEN needs to be LENGTH CHARINDEX needs to be LOCATE There probably are more differences like that but those are the two I bumped into. There's also the aforemented timestamp data type. If you use a datetime or timestamp field with getdate() as the default, you'll need to switch it to a timestamp field with a current_timestamp default. Queries are also case sensitive so make sure your column names (and, IIRC, table names) match up. I also had issues with how certain joins worked - I don't recall exactly what these issues were so I won't speculate. I just recall having to rewrite some queries to get them to function properly. --Scott ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344414 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
It honestly wasn't my intention to start any sort of flame war. I truthfully did find the comment humorous. It was like stating that this 2oz kitten is more powerful then this T-Rex over here. I had to laugh. Maybe the kitten has super-robot ninja powers? Honestly, it sounds to me like you're basing your more powerful comments off of some bad experiences you had with MySQL. I respect that, but I wouldn't call a very clearly hobbled DB engine more powerful then an enterprise class DB engine because of it. Maybe you were thinking of MS SQL Server in a more general term then MS SQL Express? -Jordan On 05/09/2011 04:20 PM, Russ Michaels wrote: Perhaps you tried to run MSSQL on linux Jordan, that would certainly be humorous I imagine :-) On Tue, May 10, 2011 at 12:12 AM, Gerald Guidogerald.gu...@gmail.comwrote: Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql Jordan Michaelsjor...@viviotech.net wrote: I find the more powerful comment humorous. This should be fun to watch :) I am making some popcorn. Anyone want some? G! On Mon, May 9, 2011 at 6:52 PM, Jordan Michaelsjor...@viviotech.net wrote: I find the more powerful comment humorous. SQL Express limits are here: http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx Migration from MS SQL to MySQL documentation is here: http://dev.mysql.com/doc/migration-toolkit/en/mysql-migration-toolkit-indepth-sourcedb-mssql.html I've done it several times with no issues. -Jordan On 05/09/2011 03:38 PM, Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql community edition so there is no need to migrate to MySQL unless your also moving to Linux. There are however free migration tools on the mysql site that will do it for you. On Mon, May 9, 2011 at 11:29 PM, Jenny Gavin-Wear jenn...@fasttrackonline.co.uk wrote: I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344416 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
lol, of course not :-) We will have to agree to disagree. I will stick with my super ninja bionic kitten, you stick with your extinct Jurassic fossil :-) On Wed, May 11, 2011 at 1:10 AM, Jordan Michaels jor...@viviotech.netwrote: It honestly wasn't my intention to start any sort of flame war. I truthfully did find the comment humorous. It was like stating that this 2oz kitten is more powerful then this T-Rex over here. I had to laugh. Maybe the kitten has super-robot ninja powers? Honestly, it sounds to me like you're basing your more powerful comments off of some bad experiences you had with MySQL. I respect that, but I wouldn't call a very clearly hobbled DB engine more powerful then an enterprise class DB engine because of it. Maybe you were thinking of MS SQL Server in a more general term then MS SQL Express? -Jordan On 05/09/2011 04:20 PM, Russ Michaels wrote: Perhaps you tried to run MSSQL on linux Jordan, that would certainly be humorous I imagine :-) On Tue, May 10, 2011 at 12:12 AM, Gerald Guidogerald.gu...@gmail.com wrote: Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql Jordan Michaelsjor...@viviotech.net wrote: I find the more powerful comment humorous. This should be fun to watch :) I am making some popcorn. Anyone want some? G! On Mon, May 9, 2011 at 6:52 PM, Jordan Michaelsjor...@viviotech.net wrote: I find the more powerful comment humorous. SQL Express limits are here: http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx Migration from MS SQL to MySQL documentation is here: http://dev.mysql.com/doc/migration-toolkit/en/mysql-migration-toolkit-indepth-sourcedb-mssql.html I've done it several times with no issues. -Jordan On 05/09/2011 03:38 PM, Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql community edition so there is no need to migrate to MySQL unless your also moving to Linux. There are however free migration tools on the mysql site that will do it for you. On Mon, May 9, 2011 at 11:29 PM, Jenny Gavin-Wear jenn...@fasttrackonline.co.uk wrote: I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344422 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
You could always both swap to a real database: http://www.oracle.com/technetwork/database/express-edition/overview/index.html :-O -- WSS4CF - WS-Security framework for CF http://wss4cf.riaforge.org/ On 11 May 2011 08:51, Russ Michaels r...@michaels.me.uk wrote: lol, of course not :-) We will have to agree to disagree. I will stick with my super ninja bionic kitten, you stick with your extinct Jurassic fossil :-) ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344423 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
They are all real databases. The majority of the problems that website databases have are caused by badly written code, inefficient queries and poor performance tuning, and have nothing to do with the database platform. On Tue, May 10, 2011 at 6:24 PM, James Holmes james.hol...@gmail.com wrote: You could always both swap to a real database: http://www.oracle.com/technetwork/database/express-edition/overview/index.html ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344428 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
You could always both swap to a real database: http://www.oracle.com/technetwork/database/express-edition/overview/index.html Your DB2 link is broken. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344434 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
don't forget that MSSQL express is also free and more powerful than mysql community edition so there is no need to migrate to MySQL unless your also moving to Linux. There are however free migration tools on the mysql site that will do it for you. On Mon, May 9, 2011 at 11:29 PM, Jenny Gavin-Wear jenn...@fasttrackonline.co.uk wrote: I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344365 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
I find the more powerful comment humorous. SQL Express limits are here: http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx Migration from MS SQL to MySQL documentation is here: http://dev.mysql.com/doc/migration-toolkit/en/mysql-migration-toolkit-indepth-sourcedb-mssql.html I've done it several times with no issues. -Jordan On 05/09/2011 03:38 PM, Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql community edition so there is no need to migrate to MySQL unless your also moving to Linux. There are however free migration tools on the mysql site that will do it for you. On Mon, May 9, 2011 at 11:29 PM, Jenny Gavin-Wear jenn...@fasttrackonline.co.uk wrote: I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344366 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql Jordan Michaels jor...@viviotech.net wrote: I find the more powerful comment humorous. This should be fun to watch :) I am making some popcorn. Anyone want some? G! On Mon, May 9, 2011 at 6:52 PM, Jordan Michaels jor...@viviotech.netwrote: I find the more powerful comment humorous. SQL Express limits are here: http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx Migration from MS SQL to MySQL documentation is here: http://dev.mysql.com/doc/migration-toolkit/en/mysql-migration-toolkit-indepth-sourcedb-mssql.html I've done it several times with no issues. -Jordan On 05/09/2011 03:38 PM, Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql community edition so there is no need to migrate to MySQL unless your also moving to Linux. There are however free migration tools on the mysql site that will do it for you. On Mon, May 9, 2011 at 11:29 PM, Jenny Gavin-Wear jenn...@fasttrackonline.co.uk wrote: I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344368 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Perhaps you tried to run MSSQL on linux Jordan, that would certainly be humorous I imagine :-) On Tue, May 10, 2011 at 12:12 AM, Gerald Guido gerald.gu...@gmail.comwrote: Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql Jordan Michaels jor...@viviotech.net wrote: I find the more powerful comment humorous. This should be fun to watch :) I am making some popcorn. Anyone want some? G! On Mon, May 9, 2011 at 6:52 PM, Jordan Michaels jor...@viviotech.net wrote: I find the more powerful comment humorous. SQL Express limits are here: http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx Migration from MS SQL to MySQL documentation is here: http://dev.mysql.com/doc/migration-toolkit/en/mysql-migration-toolkit-indepth-sourcedb-mssql.html I've done it several times with no issues. -Jordan On 05/09/2011 03:38 PM, Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql community edition so there is no need to migrate to MySQL unless your also moving to Linux. There are however free migration tools on the mysql site that will do it for you. On Mon, May 9, 2011 at 11:29 PM, Jenny Gavin-Wear jenn...@fasttrackonline.co.uk wrote: I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344370 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Well, it is pretty damn funny. I've migrated from MS SQL to MySql before and it generally isn't too bad. There are various migration tools available, I like the ones from Red Gate. MySql has some funkiness that comes into play if you want to combine foreign keys and full text indexing from what I recall, though that may have gone away in more recent versions. There are also data type differences that you might want to take a look at, like you would think that timestamp (in mysql) would be a datetime type but it isn't, so be sure to read up on them and you should be fine. If you are still looking at options, you might also want to look at PostGres. PostGres is a solidly enterprise-level db (hot swap backup, all sorts of replication options, partitioning, etc), is free, truly open source and doesn't have the strangeness that comes along with MySql being governed by Oracle. It's good stuff. Cheers, Judah On Mon, May 9, 2011 at 4:12 PM, Gerald Guido gerald.gu...@gmail.com wrote: Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql Jordan Michaels jor...@viviotech.net wrote: I find the more powerful comment humorous. This should be fun to watch :) I am making some popcorn. Anyone want some? G! On Mon, May 9, 2011 at 6:52 PM, Jordan Michaels jor...@viviotech.netwrote: I find the more powerful comment humorous. SQL Express limits are here: http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx Migration from MS SQL to MySQL documentation is here: http://dev.mysql.com/doc/migration-toolkit/en/mysql-migration-toolkit-indepth-sourcedb-mssql.html I've done it several times with no issues. -Jordan On 05/09/2011 03:38 PM, Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql community edition so there is no need to migrate to MySQL unless your also moving to Linux. There are however free migration tools on the mysql site that will do it for you. On Mon, May 9, 2011 at 11:29 PM, Jenny Gavin-Wear jenn...@fasttrackonline.co.uk wrote: I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344373 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Or possibly Jordan has needed a database that runs on more than 1 CPU, uses more than 1GB of RAM or has a db size of more than 10GB :) On Mon, May 9, 2011 at 4:20 PM, Russ Michaels r...@michaels.me.uk wrote: Perhaps you tried to run MSSQL on linux Jordan, that would certainly be humorous I imagine :-) On Tue, May 10, 2011 at 12:12 AM, Gerald Guido gerald.gu...@gmail.comwrote: Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql Jordan Michaels jor...@viviotech.net wrote: I find the more powerful comment humorous. This should be fun to watch :) I am making some popcorn. Anyone want some? G! On Mon, May 9, 2011 at 6:52 PM, Jordan Michaels jor...@viviotech.net wrote: I find the more powerful comment humorous. SQL Express limits are here: http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx Migration from MS SQL to MySQL documentation is here: http://dev.mysql.com/doc/migration-toolkit/en/mysql-migration-toolkit-indepth-sourcedb-mssql.html I've done it several times with no issues. -Jordan On 05/09/2011 03:38 PM, Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql community edition so there is no need to migrate to MySQL unless your also moving to Linux. There are however free migration tools on the mysql site that will do it for you. On Mon, May 9, 2011 at 11:29 PM, Jenny Gavin-Wear jenn...@fasttrackonline.co.uk wrote: I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344374 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
Many people often wrongly assume that MySQL is simply FREE, which is not correct. Many people are also completely unaware that there is a FREE MSSQL Express edition. The FREE version is the community edition, which also has limitations, look them up, If you want enterprise features then you have to pay i'm afraid, even with MySQL. The FREE editions of both will meet most peoples needs even with their limitations, it is really not very common to have databases of 10GB that needs more than 1GB RAM or more than 1CPU, then you probably be using the FREE editions anyway. On Tue, May 10, 2011 at 12:26 AM, Judah McAuley ju...@wiredotter.comwrote: Or possibly Jordan has needed a database that runs on more than 1 CPU, uses more than 1GB of RAM or has a db size of more than 10GB :) On Mon, May 9, 2011 at 4:20 PM, Russ Michaels r...@michaels.me.uk wrote: Perhaps you tried to run MSSQL on linux Jordan, that would certainly be humorous I imagine :-) On Tue, May 10, 2011 at 12:12 AM, Gerald Guido gerald.gu...@gmail.com wrote: Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql Jordan Michaels jor...@viviotech.net wrote: I find the more powerful comment humorous. This should be fun to watch :) I am making some popcorn. Anyone want some? G! On Mon, May 9, 2011 at 6:52 PM, Jordan Michaels jor...@viviotech.net wrote: I find the more powerful comment humorous. SQL Express limits are here: http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx Migration from MS SQL to MySQL documentation is here: http://dev.mysql.com/doc/migration-toolkit/en/mysql-migration-toolkit-indepth-sourcedb-mssql.html I've done it several times with no issues. -Jordan On 05/09/2011 03:38 PM, Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql community edition so there is no need to migrate to MySQL unless your also moving to Linux. There are however free migration tools on the mysql site that will do it for you. On Mon, May 9, 2011 at 11:29 PM, Jenny Gavin-Wear jenn...@fasttrackonline.co.uk wrote: I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344377 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Migrating a DB from MS SQL 2000 into MySQL latest release
MySql is free though licensing is a bit complicated because of a dual-license model. The community edition includes many enterprise sorts of features like replication and partitioning. If I recall, there are additional backup tools and monitoring in the paid enterprise edition. If you want to go completely free from the weird Oracle ownership stuff (which I think is wise, personally), there is the MariaDB fork which is entirely FOSS as far as I know. What enterprise features are you thinking aren't in the community edition? MySql community edition has none of the limitations present in MS SQL Express edition. Honestly, not taking advantage of more than a gig of RAM or 1 cpu core is just stupid. Why would you even have a database server? I suppose if you are housing the db on the same machine as your app server then...well, you have plenty of other problems at that point. Sql Express is great for development (though I prefer developer edition myself). It is not meant for production websites, period. That's why Microsoft has a Web edition. I like SQL Server and use it but it is wrong to try and compare Sql Express and MySql community edition, they are completely different classes of software. That being said, I still think people should check out PostGres. A feature set comparable to Oracle/MS SQL/Sybase and genuinely FOSS, unlike MySql. Tasty DB goodness. Cheers, Judah On Mon, May 9, 2011 at 4:57 PM, Russ Michaels r...@michaels.me.uk wrote: Many people often wrongly assume that MySQL is simply FREE, which is not correct. Many people are also completely unaware that there is a FREE MSSQL Express edition. The FREE version is the community edition, which also has limitations, look them up, If you want enterprise features then you have to pay i'm afraid, even with MySQL. The FREE editions of both will meet most peoples needs even with their limitations, it is really not very common to have databases of 10GB that needs more than 1GB RAM or more than 1CPU, then you probably be using the FREE editions anyway. On Tue, May 10, 2011 at 12:26 AM, Judah McAuley ju...@wiredotter.comwrote: Or possibly Jordan has needed a database that runs on more than 1 CPU, uses more than 1GB of RAM or has a db size of more than 10GB :) On Mon, May 9, 2011 at 4:20 PM, Russ Michaels r...@michaels.me.uk wrote: Perhaps you tried to run MSSQL on linux Jordan, that would certainly be humorous I imagine :-) On Tue, May 10, 2011 at 12:12 AM, Gerald Guido gerald.gu...@gmail.com wrote: Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql Jordan Michaels jor...@viviotech.net wrote: I find the more powerful comment humorous. This should be fun to watch :) I am making some popcorn. Anyone want some? G! On Mon, May 9, 2011 at 6:52 PM, Jordan Michaels jor...@viviotech.net wrote: I find the more powerful comment humorous. SQL Express limits are here: http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx Migration from MS SQL to MySQL documentation is here: http://dev.mysql.com/doc/migration-toolkit/en/mysql-migration-toolkit-indepth-sourcedb-mssql.html I've done it several times with no issues. -Jordan On 05/09/2011 03:38 PM, Russ Michaels wrote: don't forget that MSSQL express is also free and more powerful than mysql community edition so there is no need to migrate to MySQL unless your also moving to Linux. There are however free migration tools on the mysql site that will do it for you. On Mon, May 9, 2011 at 11:29 PM, Jenny Gavin-Wear jenn...@fasttrackonline.co.uk wrote: I'm interested in any info. Pit falls to avoid, best practises, etc. Many thanks, Jenny No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.900 / Virus Database: 271.1.1/3625 - Release Date: 05/08/11 19:34:00 ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344388 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
