Post MySQL Installation:

MYSQL 5.1.2600 provides you reconfiguration GUI, to reconfiguration of your database, than using command line tool. But both the formats are vital for daily uses.

 

What we got here :  Select User, Host, Password from mysql.user;

 

Step: 1

Step : 2

Step : 3

Step: 4

OR

 

Step: 5

http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html#nolinkhere

http://dev.mysql.com/doc/refman/5.0/en/innodb.html

InnoDB is a transaction-safe (ACID compliant) storage engine for MySQL that has commit, rollback, and crash-recovery capabilities to protect user data. InnoDB row-level locking (without escalation to coarser granularity locks) and Oracle-style consistent nonlocking reads increase multi-user concurrency and performance. InnoDB stores user data in clustered indexes to reduce I/O for common queries based on primary keys. To maintain data integrity, InnoDB also supports FOREIGN KEY referential-integrity constraints. You can freely mix InnoDB tables with tables from other MySQL storage engines, even within the same statement.

MySQL supports several storage engines that act as handlers for different table types. MySQL storage engines include both those that handle transaction-safe tables and those that handle nontransaction-safe tables:

• MyISAM manages nontransactional tables. It provides high-speed storage and retrieval, as well as fulltext searching capabilities. MyISAM is supported in all MySQL configurations, and is the default storage engine unless you have configured MySQL to use a different one by default.
• The MEMORY storage engine provides in-memory tables. The MERGE storage engine allows a collection of identical MyISAM tables to be handled as a single table. Like MyISAM, the MEMORY and MERGE storage engines handle nontransactional tables, and both are also included in MySQL by default.

  Note

  The MEMORY storage engine formerly was known as the HEAP engine.

• The InnoDB and BDB storage engines provide transaction-safe tables. To maintain data integrity, InnoDB also supports FOREIGN KEY referential-integrity constraints.
• The EXAMPLE storage engine is a “stub” engine that does nothing. You can create tables with this engine, but no data can be stored in them or retrieved from them. The purpose of this engine is to serve as an example in the MySQL source code that illustrates how to begin writing new storage engines. As such, it is primarily of interest to developers.
• NDBCLUSTER (also known as NDB) is the storage engine used by MySQL Cluster to implement tables that are partitioned over many computers. It is available in MySQL 5.0 binary distributions. This storage engine is currently supported on a number of Unix platforms. We intend to add support for this engine on other platforms, including Windows, in future MySQL Cluster releases.

  MySQL Cluster is covered in a separate chapter of this Manual. See Chapter 17, MySQL Cluster, for more information.

  Note

  MySQL Cluster users wishing to upgrade from MySQL 5.0 should instead migrate to MySQL Cluster NDB 6.2 or 6.3; these are based on MySQL 5.1 but contain the latest improvements and fixes for NDBCLUSTER. The NDBCLUSTER storage engine is not supported in standard MySQL 5.1 releases.

• The ARCHIVE storage engine is used for storing large amounts of data without indexes with a very small footprint.
• The CSV storage engine stores data in text files using comma-separated values format.
• The BLACKHOLE storage engine accepts but does not store data and retrievals always return an empty set.
• The FEDERATED storage engine was added in MySQL 5.0.3. This engine stores data in a remote database. Currently, it works with MySQL only, using the MySQL C Client API. In future releases, we intend to enable it to connect to other data sources using other drivers or client connection methods.

 

http://dev.mysql.com/doc/refman/5.0/en/innodb.html

Additional resources

• A forum dedicated to the InnoDB storage engine is available at http://forums.mysql.com/list.php?22.
• Innobase Oy also hosts several forums, available at http://forums.innodb.com.
• InnoDB Hot Backup enables you to back up a running MySQL database, including InnoDB and MyISAM tables, with minimal disruption to operations while producing a consistent snapshot of the database. When InnoDB Hot Backup is copying InnoDB tables, reads and writes to both InnoDB and MyISAM tables can continue. During the copying of MyISAM tables, reads (but not writes) to those tables are permitted. In addition, InnoDB Hot Backup supports creating compressed backup files, and performing backups of subsets of InnoDB tables. In conjunction with MySQL’s binary log, users can perform point-in-time recovery. InnoDB Hot Backup is commercially licensed by Innobase Oy. For a more complete description of InnoDB Hot Backup, see http://www.innodb.com/hot-backup/features/ or download the documentation from http://www.innodb.com/doc/hot_backup/manual.html. You can order trial, term, and perpetual licenses from Innobase at http://www.innodb.com/hot-backup/order/.

 

Step: 6 depending upon the installation InnoDB as mentioned before will be place in a designated folder.

Step: 7 how many hits to the server !

 

Step: 7 Server Instance Configuration

Step : 8 Character set

Step: 9

Step 10