Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
admin:indexing:creation:declaring [2012/02/02 17:44]
doc
admin:indexing:creation:declaring [2016/06/28 22:38] (current)
Line 11: Line 11:
 [[admin:​indexing:​creation:​files|Index Files]] | [[admin:​indexing:​creation:​files|Index Files]] |
 [[admin:​indexing:​creation:​performance|Performance]] [[admin:​indexing:​creation:​performance|Performance]]
 +----
 ==== Declaring Indexes ==== ==== Declaring Indexes ====
  
Line 17: Line 17:
  
  
-<​code ​sql>+<​code>​
 > create table          "​HOUSEHOLDS"​ > create table          "​HOUSEHOLDS"​
 >> ​ physical ​            "​dat/​households.dat"​ >> ​ physical ​            "​dat/​households.dat"​
Line 36: Line 36:
 Some indexes require more options or more information. ​ For example, a multi-column index - an index containing more than one column - cannot be created by simply putting a keyword next to a column. ​ These indexes can be created one of two ways.  The first, and most common way, is to declare them in the CREATE TABLE statement following all of the constraint declarations as shown in the example below. Some indexes require more options or more information. ​ For example, a multi-column index - an index containing more than one column - cannot be created by simply putting a keyword next to a column. ​ These indexes can be created one of two ways.  The first, and most common way, is to declare them in the CREATE TABLE statement following all of the constraint declarations as shown in the example below.
  
-<​code ​sql>+<​code>​
 > create table          "​HOUSEHOLDS"​ > create table          "​HOUSEHOLDS"​
 >> ​ physical ​            "​dat/​households.dat"​ >> ​ physical ​            "​dat/​households.dat"​
Line 56: Line 56:
 Omnidex indexes can also be created using CREATE INDEX statement. ​ This is a more traditional approach; however, most administrators prefer to use the CREATE TABLE statement since it is easier to differentiate which columns are indexed and which are not.  In either case, these statements only declare the indexes, but do not populate the indexes.  ​ Omnidex indexes can also be created using CREATE INDEX statement. ​ This is a more traditional approach; however, most administrators prefer to use the CREATE TABLE statement since it is easier to differentiate which columns are indexed and which are not.  In either case, these statements only declare the indexes, but do not populate the indexes.  ​
  
-<​code ​sql>+<​code>​
 > create omnidex index  "​STATE_CITY_ZIP"​ > create omnidex index  "​STATE_CITY_ZIP"​
 >> ​ on                   "​HOUSEHOLDS"​ >> ​ on                   "​HOUSEHOLDS"​
 
Back to top
admin/indexing/creation/declaring.1328204654.txt.gz ยท Last modified: 2016/06/28 22:38 (external edit)