Www.centos.org - The Community ENTerprise Operating System. MySQL vs. PostgreSQL. MySQL – is this database fit for the Enterprise? | The Register. High performance access to file storage MySQL has recently appeared as an Enterprise edition. We have already looked at whether MySQL (the company) is enterprise ready, but we can also ask whether the product itself is suitable for enterprise use. Some Reg Dev readers clearly have strong views about this already.
First up, remember that Enterprises come in all kinds of shapes and sizes. Irrespective of the exact definition, MySQL can, quite clearly, compete effectively in the small enterprise space – which means it can already service nearly 60 per cent of the working population. As an example, I talked to John Dyson, the IT director at First B2B. First B2B has a database of 24GB which runs on a four processor box with 2 GB of RAM. Dyson said: "The support is excellent; indeed it is the best support I have ever known. He is also a major fan of MySQL's Monitoring and Advisory service: "It doesn't just highlight the problem, it will supply methods of how to fix it.
Remember SQL Server 6.5? MySQL or SQL Server: Look beyond politics and hype when deciding which to use. SQL Server vs MySQL. Alexander Chigrikchigrik@mssqlcity.com IntroductionPlatform comparisonHardware requirementsSoftware requirementsPerformance comparisonTPC testsPrice comparisonFeatures comparisonT-SQL vs MySQL dialectSQL Server 2000 and MySQL v4.1 limitsConclusionLiterature Introduction Often people in newsgroups ask about some comparison of Microsoft SQL Server and MySQL. In this article, I compare SQL Server 2000 with MySQL version 4.1 regarding price, performance, platforms supported, SQL dialects and products limits.
Platform comparison SQL Server 2000 only works on Windows-based platforms, including Windows 9x, Windows NT, Windows 2000 and Windows CE. Hardware requirements To install SQL Server 2000, you should have the Intel or compatible platforms and the following hardware: MySQL version 4.1 is not so powerful as SQL Server 2000 and uses less hardware resources. Software requirements MySQL version 4.1 comes in two editions: StandardMax MySQL version 4.1 requires the following software: TPC tests Conclusion. Top Reasons for CIOs to Buy MySQL Enterprise. I don't do rants...normally. Normally, I don't do rants. But now I feel compelled to debunk the - IMO - downright slanderous post entitled "14 reasons not to use MySQL or other mid-range database management systems" by Curt Monash - an otherwise seemingly un-offensive blogger. Anyway - here's my maybe somewhat emotional analysis.
But really, this post is a load of cr*p! I mean, more than half of the "reasons" are not even about MySQL (as in the database - not the company), and the other aren't even reasons. Judge yourself. Many enterprises get quantity discounts. You make it seem like this is an advantage! Who cares if the system contains code for features you don’t need? This is not a reason to go for a high end database - merely something that might not hamper you in doing so. If you already have DBAs on staff, how much work is it to administer a few more small systems? I don't see how this is an argument to buy into high end databases. That's a load of it. MySQL Enterprise. MySQL Enterprise Edition includes the most comprehensive set of advanced features, management tools and technical support to achieve the highest levels of MySQL scalability, security, reliability, and uptime. It reduces the risk, cost, and complexity in developing, deploying, and managing business-critical MySQL applications.
MySQL Enterprise Edition includes: MySQL Enterprise Backup MySQL Enterprise Backup reduces the risk of data loss by delivering online "Hot" backups of your databases. It supports full, incremental and partial backups, Point-in-Time Recovery and backup compression. Learn More » MySQL Enterprise High Availability MySQL Enterprise High Availability enables you to make your database infrastructure highly available. Learn More » MySQL Enterprise Scalability MySQL Enterprise Scalability enables you to meet the sustained performance and scalability requirements of ever increasing user, query and data loads.
Learn More » MySQL Enterprise Authentication Learn More » Learn More » New! Mike Kruckenberg: MySQL Takes Another Step (Away from Open Source) « Pink Martini at the Oregon Zoo | Main | On Owning a Larrivée Guitar » MySQL Takes Another Step (Away from Open Source) In the ongoing effort to convert more users into paying customers, MySQL announced today that they are no longer making the source code tarball for their Enterprise server publicly available. You could see this coming from a million miles away. Back in December 2006 I pondered on the changes with the MySQL database splitting into two offerings, the enterprise and community editions: The source for the enterprise edition will still be available: we will continue to make all releases available over our BitKeeper tree and as source code tarballs So it appears that those willing to compile from source will still have access to the enterprise edition.
So where does that leave MySQL now, are they still an open source company, or have they crossed the line? So this may be true technically, but it doesn't seem to fit with the spirit of open source. Why does this matter to me? Don't try to upsell your community (Fabrizio) So apparently I’m in the right religion to be a CEO. At least, according to Amy Chua’s new book, co-written with her husband (and my former Constitutional Law professor), Jed Rubenfeld. In a nutshell, the book says that certain groups - Jews, Mormons, Indians, others - are particularly likely to be successful because of a somewhat unique combination of inferiority complex (“everybody hates us”), superiority complex (“we’re the chosen people”) and the ability to delay gratification (“real salvation comes after I die”). It’s a nice theory, and true so far as it goes.
Which may not be that far. Religion = Money? (Nope) For example, it doesn’t explain why the vast majority of Mormons aren’t leaders of nations or corporations. Maybe. But it also misses the point. All that said, I do find that religion helps me in my work, but not in the way that Chua and Rubenfeld suspect. Bold Vision, Minus the Arrogance We’re enabling engineers to build and run modern applications. A Religious Way to Succeed. MySQL « rand($thoughts); NoSQL is still not well understood, as a term or a database market category, by enterprise IT decision makers.
However, one NoSQL vendor, 10gen, creators of open source MongoDB, appears to be growing into enterprise accounts and distancing themselves from competitors. If you’re considering, or curious about, NoSQL databases, spend some time looking at MongoDB. Understanding not only SQL, aka NoSQL While the term NoSQL suggests a product category that is anti-SQL or anti-relational databases, the term has evolved to mean “not only SQL”.
According to Nosql-database.org, there are over 122 NoSQL database products to date. These products differ from traditional relational databases as they don’t rely on a relational model, are often schema free and support eventually consistent, not ACID, transactions. Max Schireson, president of 10Gen, asserts that relational databases are here to stay and have an important role to play in tomorrow’s enterprise. Slackware 12.1 installs wrong Apache build... RED HAT EXCHANGE: MySQL Enterprise Database Server. S weblog: Jeremy Cole’s take on life. » Blog Archive » Breakdown in MySQL Enterprise process. In the past few days, MySQL Community 5.0.41 was released. While reading through the changelog, I noticed the following entry: The patches for Bug #19370 and Bug #21789 were reverted.
Upon looking at Bug #21789, I noted that it was originally committed in MySQL Enterprise 5.0.32, released December 20th, 2006. The next community release which would have contained the patch is MySQL Community 5.0.33, released January 9th, 2007. This means that not only was the patch not vetted by the community, but there was a full 20 days between the enterprise release with the patch, and the next community release which contained it. The patches were rolled back in MySQL Enterprise 5.0.40, released April 17th, 2007. Back when MySQL first polled me about the community/enterprise split, I told them that this would happen. The way that RHEL and Fedora work is that all the shiny new stuff is pushed into Fedora first.
Why did MySQL reverse the process and make it (in my opinion) useless?