Would you like to work with the biggest websites and social networks in the world? Do you want to support large enterprises with their database initiatives? Would you like to assist ISVs and OEMs providing the technology that powers their products?

In the MySQL Sales Consulting organization we do just that. Oracle is hiring for MySQL Sales Consultants in multiple locations, including the US, Canada, and Romania, to support MySQL partners, customers and prospects, evangelize our products, assist marketing and cooperate with product management to shape the future of MySQL. Sound interesting? Click the following links for additional details on these openings:

• …

MySQL Connector/Net 6.7.3, a new version of the all-managed .NET driver for MySQL has been released.  This is the second beta release intended to introduce users to the new features in the release. This release is feature complete, it should be stable enough for users to understand the new features and how we expect them to work. As is the case with all non-GA releases, it should not be used in any production environment. It is appropriate for use with MySQL server versions 5.0-5.7.

After upgrading to Percona’s patched MySQL 5.1*, end users were having connectivity problems, and reporting errors such as:

OperationalError: (2003, "Can't connect to MySQL server on 'db-amo-ro' (110)")

TimeoutError: Request timed out after 5.000000 seconds

OperationalError: (1135, "Can't create a new thread (errno 11); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug")

We had these same problems a while back, before increasing ulimit settings in /etc/sysconfig/mysqld. Oracle’s MySQL startup script specifically sources this file:

[ -e /etc/sysconfig/$prog ] && . /etc/sysconfig/$prog

However, we saw these errors again when we upgraded to Percona’s MySQL 5.1. At first we thought that it was because Oracle’s startup script is /etc/init.d/mysqld and Percona’s …

Here at the MySQL Performance Blog, we’ve been discussing the several new features that MySQL 5.6 brought: GTID-based replication, InnoDB Fulltext, Memcached integration, a more complete performance schema, online DDL and …

RSVP for the North Texas MySQL User Group meeting on replication.

Date: Tuesday, June 04, 2013
Time: 5:30 PM – 7:00 PM

Oracle Corporation
6031 Connection Drive
Suite 900
Las Colinas, TX 75039-

Presented by Dave Stokes, MySQL Community Manager, Oracle Corporation

Learn how to set up MySQL replication for simple master/slave relationship, including a live demo. Then we will cover how to scale using replication and advanced strategies.

Pizza at 5:30 p.m.
Presentation begins at 6:00 p.m.

I have just posted version 3.5.2 of MyQuery on sourceforge. This version adds just one feature: The ability to run LOAD DATA LOCAL INFILE and in the process adds a few features to this, such as a progess window and the ability to stop a running load.

Download and enjoy!

/Karlsson

Log Buffer’s collection of blogs from across the world of various databases is all about nifty features, cool tricks, pragmatic tips, real world war stories, and much more.

Oracle:

Ops Center uses an Oracle Database to store product data. Normally you’ll use the Ops Center UI and won’t access the database directly, but it can occasionally be useful to see the database contents directly.

The “Oracle Fusion Financials 11g General Ledger Certified Implementation Specialist” certification is designed for implementation consultants who possess a strong foundation and expertise implementing and configuring the Fusion General Ledger application.

In …

Introduction

Transaction locks are an important feature of any transactional storage engine. There are two types of transaction locks – table locks and row locks. Table locks are used to avoid a table being altered or dropped by one transaction when another transaction is using the table. It is also used to prohibit a transaction from accessing a table, when it is being altered. InnoDB supports multiple granularity locking (MGL). So to access rows in a table, intention locks must be taken on the tables.

Row locks are at finer granularity than table level locks, different threads can work on different parts of the table without interfering with each other. This is in contrast with MyISAM where the entire table has to be locked when updating even unrelated rows. Having row locks means that multiple transactions can read and write into a single …

In a large scale mysql deployment there could be multiple masters and multiple slaves. Masters are generally in circular replication. And are used for running all inserts, updates and deletes. Slaves are used to run selects.

When you are dealing with multiple mysql instances running in a large scale environment, it is important to take care of lags between masters and slaves. To handle such

In an earlier post, I wrote about when MySQL loads data in and out of cache. At the end of this post, I talked about the concept of page churn, and having enough memory for your working set:

“If you do not have enough memory to hold all of your working set in memory, what will happen is that the buffer pool will start juggling as it churns pages out of memory only to load them back in soon after. A small amount of this is probably okay, but it can start to degrade performance. The traditional rule of thumb is called ”the 5 minute rule”. This means that if you load a page into memory and are going to need it again in the next five minutes - it should not need to be churned out.”

To be able to calculate this in a precise way we would …