Choose your database:
AnySQL
MySQL
MS SQL Server
PostgreSQL
SQLite
Firebird
Oracle
SQL Anywhere
DB2
MaxDB

Subscribe to our news:
Partners
Testimonials
Jacob Lyohne, Director of Development: "Regarding implementation, it is pretty self-explanatory and the SQLite Maestro manual is helpful for review and reference. We also found the on-line documentation useful and the software support staff readily available to answer our questions. Reports are very easy and quick to run and can be broken down into any number of statistical combinations".
Ron D.: "I'm still very happy with SQLite Maestro and Data Wizard; makes my HTPC database much easier to manage".

More

Add your opinion

SQLite Maestro online Help

Prev Return to chapter overview Next

Indexes

Indexes are primarily used to enhance database performance (though inappropriate use may result in slower performance). The key field(s) for the index are specified as column names. Multiple fields can be specified if the index method supports multicolumn indexes.
 

 

 

 

 

Use the Columns drop-down list to select a key field(s) for the index.

 

Primary key constraint

With this option checked this field becomes a compound primary key. It is useful in case the table has more than one primary key.

 

Unique constraint

Check the option to permit no duplicate values. A unique column must also define the NOT NULL attribute. A table can have one or more unique keys.

 

Unique Index

If checked, creates a unique index for the table, i.e. the database system ensures that no two rows of the specified table have the same values in the indexed columns. In this way, if two rows both contain the NULL value for all columns of an index, the two index values are not considered to be identical. If at least one column does not contain the NULL value, two rows that have the same value in all non-NULL columns are considered to be identical.



Prev Return to chapter overview Next