The convergence of telecommunications onto IP (Internet Protocol) based networks is revolutionizing today's communications industry. Communications Service Providers (CSPs) are challenged to deliver compelling new personalized services with greater agility and lower costs than ever before.

Whether they are looking to deploy new Web/Telco 2.0 applications to mobile Internet users or consolidating subscriber data within the network to support greater service personalization and targeted communications, the database plays a key role in enabling new services.

We believe MySQL is pretty much unique in the industry by providing the insight and experience to marry the innovation and speed of the Web with the proven capabilities of the carrier network. MySQL is deployed in 9 of the top 10 most trafficked sites on the web [1] including Google, Facebook and YouTube.  MySQL is also extensively deployed in the network domain, …

In my continuing MySQL 5.5 blog series, today I am covering what's new on the replication front.  MySQL replication is my favorite server feature and what drew me to MySQL during my tenure with Embarcadero Technologies.  Others seem to agree as based on community and customer surveys, MySQL replication is the most popular and widely used database feature.  Mostly because it is easy to set up and ease, it enables scalability and provides a pretty robust solution for data redundancy, backup and overall availability.  In MySQL 5.5 replication has been enhanced in response to user requests that MySQL replication:

• Ensure data consistency between master and slave servers
• Immediately detect if replication is not working
• Allow a crashed slave to automatically recover from the master relay log
• Allow users to filter …

The confusion about whether MySQL Community Edition still included InnoDB seems now to have dissipated. Thank you to Sheeri Cabral, Darren Cassar and all of you who helped correct the misperception created by catchy headlines. In part, the confusion was caused by people assuming that the MySQL Classic Edition (an option for embedding that has been around for a long time) is the same as MySQL Community Edition...not so. We have made appropriate changes to our web page to …

MySQL 5.5 is set to ship GA soon so I thought I would create a series of blogs that highlight the key new features  I will start with a rundown of where we have made improvements and then expand into details as things progress.  MySQL 5.5 merges the technical architectures of the MySQL database with the InnoDB storage engine so that the two should now be considered one and will move in tandem for the most part from now on (We can do this now that Oracle owns both...)  That said, the key things to know about MySQL 5.5 and the re-architected InnoDB storage engine are:

• Oracle's InnoDB is the default database storage engine
• Performance and Scalability on Windows is on par or better than for other platforms
  
• MySQL now fully utilizes the computing power of modern multi-core architectures across all platforms
• Replication is better and easier to monitor, manage and use …

I think most people will agree that one of the biggest advantages of MySQL Community Server is that it’s free. Being free doesn’t get you a multi-million user community though; MySQL offers a great array of transactional engines, advanced high-availability features, robust I/O performance, and it powers many of the top-500 internet sites. When it […]

Lately I’ve had to do some environment load testing so I wrote this quick script. It can be modified as needed but the basic idea is that it spawns $x threads (–threads) and then sends two connections (or however many you want with –per-connection=) per thread to the URL (–url=). You can have it wait a configurable time between connections as well (–wait=).

The url is appended with a 32 character randomized string so that any database/caching on the backend of the site isn’t serving data from a warm cache. You can hunt down the string length for 32 and change it to whatever you want. Feel free to change and use as needed, just keep my info at top.

#!/usr/bin/python
################################################################################
## DATE: 2010-10-26
## AUTHOR: Matt Reid
## MAIL: mreid@kontrollsoft.com
## SITE: http://kontrollsoft.com
## LICENSE: BSD http://www.opensource.org/licenses/bsd-license.php …

UPDATE: An on-demand replay for the webinar discussed below is available here:
http://mysql.com/news-and-events/on-demand-webinars/display-od-572.html

And there is a new whitepaper for MySQL Replication posted here:
http://mysql.com/why-mysql/white-papers/mysql-wp-replication.php

The recent announcement of the MySQL 5.5 Release Candidate included some pretty staggering increases in performance and scalability. 

Replication is also an area where many enhancements have been made including semi-synchronous replication, replication heartbeating, fsync tuning, relay log recovery, per-server replication filtering, etc.

On Tuesday 12th October, Dr. Lars Thalmann who leads the engineering team responsible for the development and implementation of these …

There’s a new version of the dbbenchmark tool available. Now we’re creating the MySQL connection pool thread count based on automatic reporting of core quantity. There is still the same method to set the thread count manually if you are interested in finding your system’s thread limits. Download the MySQL benchmarking script now and add your server performance to the community database of results!

If you’ve ever needed to know how the data and index percentages per table engine were laid out on your MySQL server, but didn’t have the time to write out a query… here it is!

select
(select (sum(DATA_LENGTH)+sum(INDEX_LENGTH))/(POW(1024,3)) as total_size from tables) as total_size_gb,
(select sum(INDEX_LENGTH)/(POW(1024,3)) as index_size from tables) as total_index_gb,
(select sum(DATA_LENGTH)/(POW(1024,3)) as data_size from tables) as total_data_gb, 

(select ((sum(INDEX_LENGTH) / ( sum(DATA_LENGTH) + sum(INDEX_LENGTH)))*100) as perc_index from tables) as perc_index,
(select ((sum(DATA_LENGTH) / ( sum(DATA_LENGTH) + sum(INDEX_LENGTH)))*100) as perc_data from tables) as perc_data,

(select ((sum(INDEX_LENGTH) / ( sum(DATA_LENGTH) + sum(INDEX_LENGTH)))*100) as perc_index from tables where ENGINE='innodb') as innodb_perc_index,
(select ((sum(DATA_LENGTH) / ( sum(DATA_LENGTH) + sum(INDEX_LENGTH)))*100) as perc_data from tables where ENGINE='innodb') as …

UPDATE: New room assignments for the MySQL Cluster and Replication Enhancements sessions

With the MySQL Sunday event at Oracle Open World rapidly approaching, and registrations to the event 10x higher than originally forecast, I thought it would be a good time to highlight sessions that are specifically addressing MySQL high availability, including MySQL Cluster .

You can see details and logistics of all of the sessions here

MySQL Cluster
Andrew Morgan and I will be presenting the latest enhancements in the world of …