Another Look at MySQL 5.1’s SQL Diagnostic Tools


 
Thread Tools Search this Thread
Top Forums Web Development MySQL DevZone RSS Another Look at MySQL 5.1’s SQL Diagnostic Tools
# 1  
Old 01-26-2009
Another Look at MySQL 5.1’s SQL Diagnostic Tools

Prior to MySQL 5.1, it wasn't all that easy to find the worst running SQL on a MySQL instance. And truth be told, MySQL still has a ways to go before it's an effortless process. But, the good news is there are some new aids in MySQL 5.1 and MySQL Enterprise that do make it more efficient to find and troubleshoot bad SQL code that's hiding inside a MySQL instance. Let's take a quick tour through these new features and see what help they provide.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Programming

[SQL] Insert content file to mysql

dear all, i want to insert string in file to mysql i just want how to do that cause i am poor in sql languages ... so this file like this DATA.txt doni|student|westjava|123412|lombok| iwan|student|westjava|1234412|utankayu| rio|student|westjava|12342|cempedak| so i want insert DATA.txt to... (2 Replies)
Discussion started by: zvtral
2 Replies

2. Shell Programming and Scripting

Convert sql output to csv file via bash tools

hi Can anybody help me with converting such structure into csv file for windows : BAT_ID ID_num CVS_LINE A_SEG SKILL_TO A_CUSTOMER_TYPE --------- ---------- --------------------------------- ---------- ------------------ ----------- 14-MAY-11 777752 ... (4 Replies)
Discussion started by: kvok
4 Replies

3. Programming

accessing mysql from ms-sql

Hi, I was trying to access Mysql Server sitting in Linux Box from MS-SQL through linked server concept. I am getting the error as : "Invalid use of schema and/or catalog for OLE DB provider 'MSDASQL'. A four-part name was supplied, but the provider does not expose the necessary... (0 Replies)
Discussion started by: DILEEP410
0 Replies

4. High Performance Computing

MySQL Cluster Administration Tools 0.3.1 (Default branch)

The MyCAT project is a toolset for managing MySQL/Linux servers, and could be helpful for anyone managing a network of *nix servers whether running MySQL Cluster, standard replication, or not running MySQL at all. At present, it contains three programs. rcall eases use and administration of groups... (0 Replies)
Discussion started by: Linux Bot
0 Replies

5. Shell Programming and Scripting

how to break mysql dump sql file

Hi folks I have mysql dump which having insert queries, i want to break that file when 10 complete "INSERTS" lines so extract that line and store in 1.sql and 2.sql and for next 10 insert lines. pls guide me how can i do that. Regards, Bash (2 Replies)
Discussion started by: learnbash
2 Replies

6. UNIX for Dummies Questions & Answers

mysql -u root < start_script.sql

what is the meaning of the line below? what is trying to be done by that line? can you explain the syntax? mysql -u root < start_script.sql (1 Reply)
Discussion started by: gfhgfnhhn
1 Replies
Login or Register to Ask a Question
SQL::Translator::Producer::MySQL(3pm)			User Contributed Perl Documentation		     SQL::Translator::Producer::MySQL(3pm)

NAME
SQL::Translator::Producer::MySQL - MySQL-specific producer for SQL::Translator SYNOPSIS
Use via SQL::Translator: use SQL::Translator; my $t = SQL::Translator->new( parser => '...', producer => 'MySQL', '...' ); $t->translate; DESCRIPTION
This module will produce text output of the schema suitable for MySQL. There are still some issues to be worked out with syntax differences between MySQL versions 3 and 4 ("SET foreign_key_checks," character sets for fields, etc.). ARGUMENTS
This producer takes a single optional producer_arg "mysql_version", which provides the desired version for the target database. By default MySQL v3 is assumed, and statements pertaining to any features introduced in later versions (e.g. CREATE VIEW) are not produced. Valid version specifiers for "mysql_version" are listed here Table Types Normally the tables will be created without any explicit table type given and so will use the MySQL default. Any tables involved in foreign key constraints automatically get a table type of InnoDB, unless this is overridden by setting the "mysql_table_type" extra attribute explicitly on the table. Extra attributes. The producer recognises the following extra attributes on the Schema objects. field.list Set the list of allowed values for Enum fields. field.binary, field.unsigned, field.zerofill Set the MySQL field options of the same name. field.renamed_from, table.renamed_from Use when producing diffs to indicate that the current table/field has been renamed from the old name as given in the attribute value. table.mysql_table_type Set the type of the table e.g. 'InnoDB', 'MyISAM'. This will be automatically set for tables involved in foreign key constraints if it is not already set explicitly. See "Table Types". Please note that the "ENGINE" option is the preferred method of specifying the MySQL storage engine to use, but this method still works for backwards compatibility. table.mysql_charset, table.mysql_collate Set the tables default charater set and collation order. field.mysql_charset, field.mysql_collate Set the fields charater set and collation order. SEE ALSO
SQL::Translator, http://www.mysql.com/. AUTHORS
darren chamberlain <darren@cpan.org>, Ken Youens-Clark <kclark@cpan.org>. perl v5.14.2 2012-01-18 SQL::Translator::Producer::MySQL(3pm)