What storage engines you can use in MySQL ?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Deepmala
    Junior Member
    • Sep 2008
    • 13

    What storage engines you can use in MySQL ?

    Following storage engines can be used in MySQL :-
    1. MyISAM
    2. HEAP
    3. MEMORY
    4. MERGE
    5. MRG_MyISAM
    6. ISAM
    7. MRG_ISAM
    8. InnoDB
    9. BDB
    10. BERKEYLEYDB
    11. NDBCLUSTER
    12. NDB
    13. EXAMPLE
    14. ARCHIVE
    15. CSV
  • Ruby17
    Member
    • Sep 2008
    • 56

    #2
    thank's for the useful information.

    Comment

    • Jenniferlinn
      Junior Member
      • Dec 2008
      • 10

      #3
      Here are some more details on the topic:

      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 non-transaction-safe tables:

      *

      MyISAM manages non-transactional 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 non-transactional tables, and both are also included in MySQL by default.


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

      The InnoDB and BDB storage engines provide transaction-safe tables. InnoDB is included by default in all MySQL 5.0 binary distributions. In source distributions, you can enable or disable either engine by configuring MySQL as you like.
      *

      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.

      #

      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.

      When you create a new table, you can specify which storage engine to use by adding an ENGINE or TYPE table option to the CREATE TABLE statement:

      CREATE TABLE t (i INT) ENGINE = INNODB;
      CREATE TABLE t (i INT) TYPE = MEMORY;

      The older term TYPE is supported as a synonym for ENGINE for backward compatibility, but ENGINE is the preferred term and TYPE is deprecated.

      If you omit the ENGINE or TYPE option, the default storage engine is used. Normally, this is MyISAM, but you can change it by using the --default-storage-engine or --default-table-type server startup option, or by setting the default-storage-engine or default-table-type option in the my.cnf configuration file.

      You can set the default storage engine to be used during the current session by setting the storage_engine or table_type variable:

      SET storage_engine=MYISAM;
      SET table_type=BDB;

      When MySQL is installed on Windows using the MySQL Configuration Wizard, the InnoDB storage engine can be selected as the default instead of MyISAM.

      Comment

      • mathewh
        Junior Member
        • Dec 2008
        • 1

        #4
        Web Development

        Hi frnd,
        If you are looking for a Web Development team that has extensive experience with the following technologies web 2.0, e-commerce. My/MS SQL.
        Then you must visit to the link given below, resulting you would get good team
        for web development.
        I need your comments about it.
        Please make and advice - which one is best.

        Thanks for your time!

        Comment

        • eey123
          Junior Member
          • Dec 2009
          • 5

          #5
          I think this is a good advice

          Comment

          Working...
          😀
          😂
          🥰
          😘
          🤢
          😎
          😞
          😡
          👍
          👎