This depends on the way you plan to access the table. Indexing reduces the effect of table scans, or where clauses. If you will not be fetching records by finding a value in a given field, do not add that field to any supplemental indexes. Indexes slow the database down when writing, since each index must be maintained.
**************** I am debating the performance gains to be realized, if any, by indexing a particular table in a system implementation for which I am responsible. __________ This is the table creation command: CREATE TABLE CC ( [catIndex] [integer] NOT NULL, [contIndex] [integer] NOT NULL, [new] [integer] NOT NULL DEFAULT(0)); Pretty simple: a table containing 3 fields, all integers. __________ If I were to index this table, I would implement this index creation command: CREATE UNIQUE INDEX CC_CatContNewIndex on CC ([catIndex] ASC, [contIndex] ASC, [new] ASC); Pretty simple: an index containing 3 fields, all integers, sorted ascending order. __________ The question: Could improvements in search and access performance be realized by indexing this table? Or, might having an index actually decrease table write and/or read performance? Thanks, Lee _______________________________________________ _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
