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.com>wrote: > > 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+tables&ie=utf-8&oe=utf-8&aq > =t&rls=org.mozilla:en-GB:official&client=firefox-a<http://www.google.co.uk/search?q=mysql+corrupted+tables&ie=utf-8&oe=utf-8&aq%0A=t&rls=org.mozilla:en-GB:official&client=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.com>wrote: > > > > > 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 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.com > > > >wrote: > > > > > > > >> > > > >> 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-indept > > h-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:344411 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
