Hopefully if my question has run out of context everyone will allow me to go by.I'm not good whatsoever if this involves DBMS and all sorts of i'm able to till during my 7+ many years of IT experience has the capacity to write some fundamental queries (with the aid of Google).

I'm focusing on my very own project and i'm all completed with the look phase and incredibly will obvious what all table structure i have to have for that project.I will use MySQL with this and also, since project is by using the abilities of small Content management systems by itself meaning lots of data to become handled in the database size.

I'm using TOAD for MySQL to produce schema along with other things for MySQL but while carrying this out i've couple of queries which i wish to address at first.

  1. What ought to be the storage engine type for MySQL (default is InnoDB)
  2. Every other parameters must taken proper care of storage Engine
  3. what Character set and Collation have to be set at table level as well as for column level if any (Application will need to take proper care of internationalization )

being very little experienced in the database aspect fundamental essentials question keep popping i believe and then any help in connection with this is going to be appreciated.

You need to stick to InnoDB. It's transactions along with a row-level securing. For top (writing) concurrency the row-level securing enables multiple Card inserts/UPDATEs/Removes simultaneously. MyIsam has table-securing, meaning just one modifying query at any given time. If you are read-heavy, MyISAM may perform better though. SELECT COUNT(*) FROM table; for instance is really a record factor MyISAM can answer instantly, while InnoDB really does a COUNT(). InnoDB allows you define connections involving the tables (Foreign Key Constraints) that will help you together with your data integrity.

If you are thinking about such things as the above mentioned, I suggest reading through High End MySQL from O'Reilly Media.

Concerning the Character Set you need to make certain that tables / posts make use of the same character set. Ideally Unicode (UTF8). Make certain your mysql client can also be established to use UTF8, to prevent (transparent) transliteration of the data. (Actually, make certain the entire application does UTF8 from storage to show).

The Collation is one thing that allows you define your text being UTF8, however in a, say, German, context. With this understanding, MySQL will correctly sort "fööbar" and "foobar" based on the rules from the German language. (sorting among other activities). It's my job to use "utf8_general_ci". Take a look at some good examples at mysql: http://dev.mysql.com/doc/refman/5.0/en/charset-collation-effect.html

Most likely you're going to get better answer, but rapidly from the encounters:

  1. InnoDB will work for creating reliable data-driven web application and MyISAM will work for performance. But InnoDB supports Foreign Secrets, transactions and row-level-securing making you honest while creating tables. This means if you won't want to produce a easy and experimental database, the answer is applying InnoDB.
  2. You should think about Foreign Keys, transactions and Row-level securing (Only InnoDB supports these functions)
  3. utf8_general_ci is easily the most popular one I understand if you wish to storage different languages' data. It will not allow you to lower.

I really hope this help.