Skip to main content

Table Indexing


When a row is inserted into a table, the database server does not attempt to put the data in any particular location within the table.  Instead, the server simply places the data in the next available location within the file.  When a query is sent against the table therefore, the server will need to inspect every row of the table to answer the query.  Tables in MySQL can grow very large, and as a table gets bigger, retrievals from it become slower. 

An index in MySQL serves to assist in finding row data more quickly and easily, much like an index in the back of a technical manual.  Database indexes are used to locate rows in a table.  Indexes are special structures that, unlike normal tables, are kept in a specific order.  Instead of containing all of the data about an entity, however, an index contains only the column(s) used to locate rows in the data table.  It also contains information describing where the rows are physically located.  Usually, all the indexes required are created when the tables are created. Indexes can be created on single columns or multiple columns (composite indexes).  For example, the phone number for an individual in a phone book would use a single index, whereas the  last_name and first_name would be grouped together as a composite index. 

Types of Indexes: 


MySQL supports several general types of indexes: 


PRIMARY KEY 


1.  Only one PRIMARY KEY is allowed per table 
2.  Uniquely identifies a single row in the table 
3.  No  NULL values are allowed 
4.  If a duplicate value is INSERTed or UPDATED MySQL will return an error  


UNIQUE (same rules as the PRIMARY KEY with two exceptions) 


1.  Allows values stored as NULL 
2.  Can have multiple UNIQUE indexes in a table 
3.  Each NON-NULL value uniquely identifies a single row in a table 


INDEX - Allows multiple identical values 


Example: 


CREATE TABLE `countrylanguage` ( 
               `CountryCode` char(3) NOT NULL default '', 
               `Language` char(30) NOT NULL default '', 
               `IsOfficial` enum('T','F') NOT NULL default 'F', 
               `Percentage` float(4,1) NOT NULL default '0.0', 
                PRIMARY KEY  (`CountryCode`,`Language`) 
                ) ENGINE=MyISAM COMMENT 'Lists Languages Spoken' 

Comments

Popular posts from this blog

PHP INTRODUCTION

                     PHP  (recursive acronym for  PHP: Hypertext Preprocessor ) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. PHP stands for  P HP:  H ypertext  P reprocessor PHP is a server-side scripting language, like ASP PHP scripts are executed on the server PHP supports many databases (MySQL, Informix, Oracle, Sybase, Solid, PostgreSQL, Generic ODBC, etc.) PHP is an open source software PHP is free to download and use Why PHP? PHP runs on different platforms (Windows, Linux, Unix, etc.) PHP is compatible with almost all servers used today (Apache, IIS, etc.) PHP is FREE to download from the official PHP resource:  www.php.net PHP is easy to learn and runs efficiently on the server side What can PHP do? Anything. PHP is mainly focused on server-side scripting, so you can...

SQL Joins

1. Login in to the mysql client using the login name and password provided by your instructor (if not already logged in). 2. View the existing databases that the MySQL Server is maintaining. SHOW DATABASES; 3. Utilize the photo_album database. USE photo_album; ---- If Need be, recreate the database and load the SQL data in that will be used for this lab CREATE DATABASE photo_album; SOURCE /tmp/photo_album.sql; 4. Query the database to display the active primary customer (email, first and last name) and all the associated active login names associated with that customer. SELECT customers.email_customer, customers.fname, customers.lname, logins.login_name  FROM customers, logins WHERE customers.email_customer = logins.email_customer  AND customers.active_customer = 'True'  AND logins.active_login = 'True';

Storage Engine Breakdown

The following diagram represents a simplified view of the MySQL server and its interaction with the  storage engines. The following properties are storage engine dependant: • Storage Medium – Each table uses its own method of storing the data it contains. • Transactional Capabilities – Certain storage engines handle transactional processing which ensures that integrity of a database is maintained during the processing of multiple SQL statements.