Let’s extend the analysis of MySQL parallel query processing with InfiniDB against 60 Billion rows:

The Star Schema Benchmark scale factor for 10k generates 60 billion rows fact rows, with the largest dimension tables at 300 million and 100 million.  Previous results were shown at a scale factor of 1000, generating 6 billion facts and 30 millRead More...

This morning I checked planet.mysql.com and to my surprise I found that a topic from our (Webyog) Forums (http://www.webyog.com/forums/index.php?showtopic=5066) was syndicated to planet.mysql.com.  I am not able to understand how that could happen. To my best knowledge I never asked for it. However I do not mind personally if somebody else found a way to syndicate this particular post. It may be useful for somebody. But who owns the right to syndicate that Forums topic really? The user that originally posted in our Forums? Me? Or Santa Claus maybe? I would not do myself without the accept from the poster of the topic.

In our Blog (http://www.webyog.com/blog) we have an option to set a ‘mysql’ category for a post.  What posts appear marked with that category get syndicated. Until now …

As I wrote about 2 years ago the feature of Innodb to store copy of master's position in Slave's Innodb tablespace got broken. There is a lot of discussions at the corresponding bug report while outcome of the fix remained uncertain for me (the bug is market duplicate while the bugs it seems to be duplicate for describe different issues).
Anyway. The customer came to me today having the following message in the error log after Slave crash while running MySQL 5.1.41 (extra virgin version without XtraDB or Percona Patches)

InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 0 10000000, file name mysql-bin.005000
InnoDB: Last MySQL binlog file position 0 20000000, file name ./mysql-bin.003000

He …

MySQL Connector/Net 6.3.0, a new version of the all-managed .NET driver
for MySQL has been released. This is an alpha release and is intended to
introduce you to the new features and enhancements we are planning. This
release should not be used in a production environment.

It is now available in source and binary form from
[http://dev.mysql.com/downloads/connector/net/6.3.html] and mirror sites
(note that not all mirror sites may be up to date at this point of time
- if you can’t find this version on some mirror, please try again later
or choose another download site.)

New features or changes:

• Visual Studio 2010 RC support
• Nested transaction scope support

What we know may be broken

• Documentation is not …

I have been a little bit stubborn on my concession that cloud computing is really going to be the wave of the future. Though lately I have been playing with a lot of cloud related technologies and am hooked. Spin up 10 (or 100) Linux servers in a minute from a web page with no real systems management skills and then you start seeing the power of cloud computing. As I try to get smarter on cloud computing I compiled the following list of resources that I have found helpful.  If you have a great cloud resource please feel free to let me know what I am missing on.

Cloud and Virtualization Guides and Whitepapers

• …

I sound like a broken record with every client when I talk to about the resilience of their production environments. It’s very simple in theory, however in practice many organizations fail.

Ask yourself these checklist questions for your MySQL backup and recovery process?

1. Do you have MySQL backups in place?
2. Do you backup ALL your MySQL data?
3. Do you have consistent MySQL backups?
4. Do you have backups that include both static snapshot and point in time transactions?
5. Do you review your backup logs EVERY SINGLE day or have tested backup monitoring in place?
6. Do you perform a test recovery of your static backup?
7. Do you perform a test recovery to point in time?
8. Do you time your backup and recovery process and review over time?
9. Do you have off-site copies of your backups?
10. Do you backup your primary binary logs?
…

While working with the MySQL Enterprise Dashboard I found a small problem when trying to use the Query Analyzer. The test server I am running on had a user used by the dev team that had the following privileges:

GRANT USAGE ON *.* TO 'test_user'@'10.18.%' IDENTIFIED BY PASSWORD 'HASHNOTGIVEN';
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, SHOW VIEW, TRIGGER ON `canoe`.* TO 'test_user'@'10.18.%';
GRANT SELECT on `mysql`.`proc` TO 'test_user'@'10.18.%';

I the agent running on this server is mysqlmonitoragent-2.1.0.1093 and the proxy has been set to receive connections on the default port, 6446. When I try to connect I received the following error:

shell> mysql -utest_user -p --host=m120649.ningops.com --port=6446
Enter password:
ERROR 1045 (28000): Access denied for user 'test_user'@'localhost' (using password: YES)

I …

ProblemA customer recently showed up with the following problem:
With your guidelines [1] I am now able to send the MySQL error log to the syslog
and in particular to an external log server.
But I cannot see which user connects to the database in the error log.

How can I achieve this?
IdeaDuring night when I slept my brain worked independently on this problem and in the morning he had prepared a possible solution for it.

What came out is the following:

• We create an UDF which allows an application to write to the MySQL error log.
  See my previous article about this [2].
  
• We specify in a simple SQL query how the string should look which we want to write to the MySQL error log file.
  
• We use the init_connect [3] hook (= logon trigger) which MySQL provides to log the information to the error log.
  

How to solve …

Problem

A customer recently showed up with the following problem:

With your guidelines [1] I am now able to send the MySQL error log to the syslog and in particular to an external log server.
But I cannot see which user connects to the database in the error log.

How can I achieve this?

Idea

During night when I slept my brain worked independently on this problem and in the morning he had prepared a possible solution for it.

What came out is the following:

• We create an UDF which allows an application to write to the MySQL error log.
  See my previous article about this [2].
• We specify in a simple SQL query how the string should look which we want to write to the MySQL error log file.
• We use the init_connect [3] hook (= logon trigger) which MySQL provides to log the information to the error log.

…

Problem

A customer recently showed up with the following problem:

With your guidelines [1] I am now able to send the MySQL error log to the syslog and in particular to an external log server.
But I cannot see which user connects to the database in the error log.

How can I achieve this?

Idea

During night when I slept my brain worked independently on this problem and in the morning he had prepared a possible solution for it.

What came out is the following:

• We create an UDF which allows an application to write to the MySQL error log.
  See my previous article about this [2].
• We specify in a simple SQL query how the string should look which we want to write to the MySQL error log file.
• We use the init_connect [3] hook (= logon trigger) which MySQL provides to log the information to the error log.

…