What lead developer or Architect should know before starting the project/Product – Part2

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

Default MYSQL EngineFast for reading and insertingTable level lock Fulltext searching capabilitiesNo transactional integrity (ACID compliance)No rollback abilitiesNo Foriegn keys and cascading deletes and updatesRow limit of 4,284,867,296 rowsMaximum of 64 indexes per row

When to use MyISAM? -MyISAM is designed with the idea that your database is queried far more than its updated and as a result it performs very fast read operations. If your read to write(insert|update) ratio is less than 15% then you should use MyISAM.

INNOBD Fast for updating Transactional integrity (ACID compliance)Row level locksForiegn keys and cascading deletes and updatesForiegn keys and cascading deletes and updatesNo full text indexingCannot be compressed for fast, read-only

When to use INNOBD? -INNOBD is designed with the idea that your database is concurrent insert/Update and raea data same time with the suppot of the Transaction and Foriegn keys. If your using any ecommarce or other sensitive information then you should use INNOBD.

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. Experimental support for Windows is available beginning in MySQL Cluster NDB 7.0; however, we do not intend to backport this functionality to MySQL 5.0

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

Some Command for MYSQL EngineHow to change MYSQL Engine- ALTER TABLE prosatya ENGINE = innodb;Which MYSQL engine support you database - SHOW ENGINES; 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

Default MYSQL EngineFast for reading and insertingTable level lock Fulltext searching capabilitiesNo transactional integrity (ACID compliance)No rollback abilitiesNo Foriegn keys and cascading deletes and updatesRow limit of 4,284,867,296 rowsMaximum of 64 indexes per row

When to use MyISAM? -MyISAM is designed with the idea that your database is queried far more than its updated and as a result it performs very fast read operations. If your read to write(insert|update) ratio is less than 15% then you should use MyISAM.

INNOBD Fast for updating Transactional integrity (ACID compliance)Row level locksForiegn keys and cascading deletes and updatesForiegn keys and cascading deletes and updatesNo full text indexingCannot be compressed for fast, read-only

When to use INNOBD? -INNOBD is designed with the idea that your database is concurrent insert/Update and raea data same time with the suppot of the Transaction and Foriegn keys. If your using any ecommarce or other sensitive information then you should use INNOBD.

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. Experimental support for Windows is available beginning in MySQL Cluster NDB 7.0; however, we do not intend to backport this functionality to MySQL 5.0

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

Some Basic Command of MYSQL every developer should know -MySQL command prompt login - mysql –hhost –uuser –ppassword;How to change MYSQL Engine- ALTER TABLE prosatya ENGINE = innodb;Which MYSQL engine support you database - SHOW ENGINES; Show database - show databases;Select database - Use databaseName ; Display all of tables in database - Show tables ;Display table structure – DESCRIBE TableName ; or DESC TableName; For table or query performance - EXPLAIN select * from tbl_users where id=1 ;

* InnoDB* MyISAM* Mysql* Sysadmin

* InnoDB

* MyISAM* Mysql* Sysadmin