The MySQL Telecom sales team is a global team, but it happens to be organized under the EMEA region of the MySQL sales department. Since the EMEA region is having a staff meeting in Dublin this week, it means also we in the telecom team are gathered here. A good opportunity to meet your globally dispersed collagues.

Zack Urlocker was the special guest star from headquarters. He presented a freudian-slip-slide saying that MySQL 5.1 will be released GA in July 2009. After lots of laughter he concessed that maybe engineering can pull it of faster, like maybe July 2008.

Another hot topic Zack talked about was to review how the integration with Sun is going...

...we concluded at least some of us are adapting just fine :-)

Sheeri Cabral, an active MySQL blogger and two-time winner of MySQL Community Contributor awards has written a great review on MONyog.

Read the full review here

Our favorite highlights:

As an overall review — MONyog is the best out-of-the-box GUI monitoring tool for MySQL that I have seen. It “just works.” As promised, getting up and running quickly is easy, and having a centralized location for monitoring is very useful. The graphs are beautiful and the statistics that are graphed are useful time-savers.

The biggest difference between MySQL’s Enterprise Monitor and MONyog is that MONyog is agentless. At Pythian, we have many clients with differing security requirements. Requiring a daemon process to be running is not something we currently do, and it might be a hard sell for some clients. Even if every client was …

Bug fixes and Enhancements:

• Optimized SFTP code. This means that the Log Analyzer is now several times faster than previous Betas
• Fixed an issue with trending
• Log file parsing issue with MySQL 5.1.x resolved

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

When writing scripts for running MySQL in batch mode, it is often desired to be able to change the SQL queries on-the-fly so that we can use the script to solve more generic problems.

For example, I need to use my script for different storage engines and table names and I want to be able to do it at runtime instead of manually changing my script every time.

Here is how I do it:

I have a template file which is my script but with the variables having generic names. In this case, I have considered plugin_name as the storage engine name , and table_name as the table name.

Consider the following script:

# automation-script-template
# Mixing shell commands and SQL queries in batch mode- demo script

# Replace variables: plugin_name, table_name with appropriate names- done automatically by …

When writing scripts for running MySQL in batch mode, it is often desired to be able to change the SQL queries on-the-fly so that we can use the script to solve more generic problems.

For example, I need to use my script for different storage engines and table names and I want to be able to do it at runtime instead of manually changing my script every time.

Here is how I do it:

I have a template file which is my script but with the variables having generic names. In this case, I have considered plugin_name as the storage engine name , and table_name as the table name.

Consider the following script:

# automation-script-template
# Mixing shell commands and SQL queries in batch mode- demo script

# Replace variables: plugin_name, table_name with appropriate names- done automatically by …

The MySQL Telecom sales team is a global team, but it happens to be organized under the EMEA region of the MySQL sales department. Since the EMEA region is having a staff meeting in Dublin this week, it means also we in the telecom team are gathered here. A good opportunity to meet your globally dispersed collagues.

Zack Urlocker was the special guest star from headquarters. He presented a freudian-slip-slide saying that MySQL 5.1 will be released GA in July 2009. After lots of laughter he concessed that maybe engineering can pull it of faster, like maybe July 2008.

Another hot topic Zack talked about was to review how the integration with Sun is going...

...we concluded at least some of us are adapting just fine :-)

The MySQL Telecom sales team is a global team, but it happens to be organized under the EMEA region of the MySQL sales department. Since the EMEA region is having a staff meeting in Dublin this week, it means also we in the telecom team are gathered here. A good opportunity to meet your globally dispersed collagues.

Zack Urlocker was the special guest star from headquarters. He presented a freudian-slip-slide saying that MySQL 5.1 will be released GA in July 2009. After lots of laughter he concessed that maybe engineering can pull it of faster, like maybe July 2008.

Another hot topic Zack talked about was to review how the integration with Sun is going...

...we concluded at least some of us are adapting just fine :-)

Progress acquires IONA. Red Hat announces quarterly earnings. Optaros raises new round of funding. (and more)

Progress Software Corporation to Acquire IONA Technologies, Progess Software / IONA Technologies (Press Release)

Red Hat Reports First Quarter Results, Red Hat (Press Release)

Optaros Closes $12 Million in Series C Financing Co-Led by .406 Ventures & Globespan Capital Partners, Optaros (Press Release)

Sourcefire, Inc. Responds to Barracuda Networks …

Yesterday I blogged about the MySQL Challenge to limit rows accessed. Sheeri had some great comments about the subject, but didn't know either why the first 4 rows were not counted in my original solution:

mysql> explain select actor_id from actor where actor_id % 5 = 0 and actor_id < 26;

*************************** 1. row ***************************
id: 1
select_type: SIMPLE
table: actor
type: range
possible_keys: PRIMARY
key: PRIMARY
key_len: 2
ref: NULL
rows: 20
Extra: Using where; Using index

mysql>

I've been thinking about this some more, and wondered what would happen if I tried this query:

mysql> select actor_id from actor where actor_id …

Yesterday I blogged about the MySQL Challenge to limit rows accessed. Sheeri had some great comments about the subject, but didn't know either why the first 4 rows were not counted in my original solution:

mysql> explain select actor_id from actor where actor_id % 5 = 0 and actor_id < 26;

*************************** 1. row ***************************
id: 1
select_type: SIMPLE
table: actor
type: range
possible_keys: PRIMARY
key: PRIMARY
key_len: 2
ref: NULL
rows: 20
Extra: Using where; Using index

mysql>

I've been thinking about this some more, and wondered what would happen if I tried this query:

mysql> select actor_id from actor where actor_id …