So far, I have been blogging about curious RDBMS caveats mostly related to Oracle and MySQL databases. Some examples: You never stop learning about Oracle features NOT IN vs. NOT EXISTS vs. LEFT JOIN / IS NULL: MySQL SQL incompatibilities: NOT IN and NULL values MySQL Bad Idea #384 But there are also other databases, … Continue reading 10 Things in SQL Server Which Don’t Work as Expected →

Not so far I have found new cool tool to work with mySQL – Valentina Studio. Its free edition can do things more than many commercial tools!!
I very recommend check it. http://www.valentina-db.com/en/valentina-studio-overview

The MySQL for Developers course examines the tools used by MySQL development professionals. Expert instructors reference real-world examples when illustrating how to generate complex queries, and consume them in your application. This course covers Java and PHP languages.

You can take this course as:

• A Live-Virtual event: Take this course from your own desk, no travel required. Choose from a wide selection of events on the schedule to suit different timezones.
• An In-Class event: Travel to an education center to take this class. Below is a selection of in-class events already on the schedule.

I attended Percona Live London since the creation of the event, and every year, I left with the same feeling, a great satisfaction.
This year again PLUK will be the place to be for MySQL lovers in Europe and I hope to meet you there.

Let me explain why you should go to PLUK2013?

• Because MySQL is primarily a community
• And you are this community
• This is an easy way to meet other members of this community
• You can meet talented people behind the blogs you read every days
• And speakers from some of the most innovative companies with MySQL
• This is the largest MySQL event in Europe
• London is really a fantastic city even in November (there is no season for beer)
• You can save a lot of money until August 4

Register now and enjoy …

MySQL Server has an aborted_connect status counter which will show you the number of failed attempts to establish a new connection.  The manual describes potential causes as follows:

• A client does not have privileges to connect to a database.
• A client uses an incorrect password.
• A connection packet does not contain the right information.
• It takes more than connect_timeout seconds to get a connect packet. See Section 5.1.4, “Server System Variables”.

It goes on to make the following statement:

If …

Change Password Of Server OpenSUSE 12.2 With ISPConfig 3

In this tutorial we will show you how to change the password of your mail server which is running on OpenSUSE 12.2 and ISPConfig 3.x.

It is time for the Query Tuning Webinar again! This year I will be delivering the Webinar on July 24 at 10 a.m. PDT, Advanced MySQL Query Tuning, hosted by Percona. I have included some new topics about loose and tight index scan and will also show some real world examples and solutions for MySQL query optimizations.

You can register for the Webinar here. It will also be recorded, so if you can’t make it on July 24, 10am you can always watch it later.

This week we talk with Tim Callaghan of Tokutek about TokuMX, a take on MongoDB. Ear Candy is perror on Windows and At the Movies is a presentation from the SkySQL and MariaDB Solutions Day 2013 about Tokutek.

TokuMX

Replication between MySQL and MongoDB using Tungsten a couple of years ago at Open DB Camp in Sardinia (2011).

Previous interviews with Tokutek folks in:
Episode 39

read more

In writing a recommendation for our Web development team on how to use MySQL, I came up with the following list, which I want to share: What kind of queries are bad for MySQL?

• Any query is bad. Send a query only if you must. (Hint: use caching like memcache or redis)
• Queries that examine many rows are bad. Try instead to use…
  

      SELECT col1 FROM table1 WHERE primary_key_column=SOMETHING

  
  . Or at least
  

  secondary_key_column=SOMETHING

  
  . If it is still not possible, try to make the query examine the least amount of rows possible (zero is ideal, as we come to the first case here)
• Queries with JOINS are bad. Try to denormalize the table to avoid JOINS. Example: original query
  

      SELECT t2.value FROM t2 JOIN t1 ON (t1.id=t2.tid) WHERE t1.orderdate=NOW()

  
  . This can be denormalized by copying the column orderdate from table …