New MySQL Enterprise with Query Analyzer Boosts Database Application Performance


 
Thread Tools Search this Thread
Top Forums Web Development MySQL DevZone RSS New MySQL Enterprise with Query Analyzer Boosts Database Application Performance
# 1  
Old 11-19-2008
New MySQL Enterprise with Query Analyzer Boosts Database Application Performance

Sun Microsystems, Inc. today announced a major new version of its MySQL Enterprise™ subscription service to help corporate users dramatically improve the speed and uptime of their MySQL™ database applications. MySQL Enterprise subscribers now have access to Sun's new MySQL Query Analyzer tool for monitoring query performance to accurately pinpoint and correct problem SQL code -- in addition to MySQL Enterprise's regular software updates and 24x7 production technical support.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Problems with PHP query to MySQL database

Hello all, I completed a website (it was code by php) and putted it to AWS, I install fedora instance in EC2 with the base is php and mysql. I putted all files of my website to folder /home/webuser/helloworld/htddocs and my database (mysql) to folder /var/lib/mysql/test ("test" is my... (2 Replies)
Discussion started by: hero132
2 Replies
Login or Register to Ask a Question
Apache::Session::Lock::MySQL(3pm)			User Contributed Perl Documentation			 Apache::Session::Lock::MySQL(3pm)

NAME
Apache::Session::Lock::MySQL - Provides mutual exclusion using MySQL SYNOPSIS
use Apache::Session::Lock::MySQL; my $locker = Apache::Session::Lock::MySQL->new(); $locker->acquire_read_lock($ref); $locker->acquire_write_lock($ref); $locker->release_read_lock($ref); $locker->release_write_lock($ref); $locker->release_all_locks($ref); DESCRIPTION
Apache::Session::Lock::MySQL fulfills the locking interface of Apache::Session. Mutual exclusion is achieved through the use of MySQL's GET_LOCK and RELEASE_LOCK functions. MySQL does not support the notion of read and write locks, so this module only supports exclusive locks. When you request a shared read lock, it is instead promoted to an exclusive write lock. CONFIGURATION
The module must know how to connect to your MySQL database to acquire locks. You must provide a datasource name, a user name, and a password. These options are passed in the usual Apache::Session style, and are very similar to the options for Apache::Session::Store::MySQL. Example: tie %hash, 'Apache::Session::MySQL', $id, { LockDataSource => 'dbi:mysql:database', LockUserName => 'database_user', LockPassword => 'K00l' }; Instead, you may pass in an already opened DBI handle to your database. tie %hash, 'Apache::Session::MySQL', $id, { LockHandle => $dbh }; AUTHOR
This module was written by Jeffrey William Baker <jwbaker@acm.org>. SEE ALSO
Apache::Session perl v5.10.1 2010-10-18 Apache::Session::Lock::MySQL(3pm)