http://www.slideshare.net/techdude/how-to-kill-mysql-performance

If you’re an Anchor customer, I should point out that the ARCHIVE storage engine isn’t available in Redhat’s version of MySQL, which is a damned nuisance.

So here you go a straight to the point post that will give you:

• a fully functional MySQL databse schema along with inserted dummy data
• a relational database with common relationships such as one to one, one to many and many to many
• a list of example select queries to use to see how you can create table joins between tables

To download the database please click here

Diagram Of The Database
The following diagram will help give you a good visual of all the tables in the database and what relationships are in place:

Select Queries
So you have got all your information in different tables (relational database) and you need to perform table joins. Below are a list of the most common types of table joins using the different relationship types one-to-one, one-to-many and many-to-many:

One-To-One

SELECT dog.id, dog.name, rfid_dog.bar_code AS rfid
FROM dog,rfid_dog
WHERE dog.id = rfid_dog.dog_id
ORDER BY dog.name ASC;


One-To-Many

SELECT dog.id,dog.name,breed.name AS breed
FROM dog,breed
WHERE dog.breed_id = breed.id
ORDER BY dog.name ASC;


Many-To-Many

SELECT breeder.name,breeder.address,breeder.phone,breeder.email,breed.name AS breedName
FROM breed,breeder,breed__breeder
WHERE breed__breeder.breed_id = breed.id
AND breed__breeder.breeder_id = breeder.id
ORDER BY breeder.name ASC;


And just like that you now have your head around relational databases!

If you have come to this point and your still excited and want to learn more please see our wiki article which goes into more detail about relational databases plus talks about optimisation techniques to speed things up.

The script does good things, but MySQL could probably be doing things better to begin with – make it more secure out-of-the-box, and the last thing they should be doing is shipping it with an empty root password. >_< It pains me to say it, but I think MSSQL probably comes with a more-secure initial configuration. Things like no remote connections, and no test database unless you explicitly ask for it.

The documentation for mysql_secure_installation is brief but functional. One of the things I thought it was doing was writing out a convenient .my.cnf file for the user, but it turns out it just deletes it once it’s finished. This is a shame, because the per-user config file is really cool.

If you’re not already taking advantage of them, you should. MySQL calls them “option files”, and it lets you set default parameters for the client apps you use at the command line, like mysql and mysqldump, etc. We use them to store root’s login credentials so we don’t have to lookup the password for a given machine, then mess around with mysql’s asinine option-handling.

It’s best to at least read up briefly on option files before using them, but they’re pretty straightforward: you have “groups” of options in the file written as [groupname], then one option on each line after that. An instructive example:

[mysql]
database=mysql



[client]
user=root
password=verySecurePassword


If you’re going to keep your password here, you must make sure the file is adequately protected from other users who might try to view it.

The group-names I mentioned correspond to the client program that will use the options. [client] is a special case; those options will be used by all the mysql client programs, so it’s the ideal place for your username and password.

Having the database option in the [mysql] group means you’re automatically connected to a database once you start the mysql command-line client. We don’t put this in the [client] group because it would affect other utilities like mysqldump.