ODBC Server Reference Manual

Transact-SQL Language
HP NonStop ODBC Server Reference Manual—429151-002
4-52
Examples
WITH FILLFACTOR = fill
is not supported. In the NonStop ODBC Server, this clause is ignored. No error
messages are generated.
WITH IGNORE DUP KEY
is not supported. In the NonStop ODBC Server, this clause is ignored. No error
messages are generated. Rows are rejected if they have a duplicate primary key.
WITH IGNORE DUP ROW, WITH ALLOW DUP ROW
is not supported. In the NonStop ODBC Server, this clause is ignored. No error
messages are generated. Rows are rejected if they are not unique with respect to
the index and the index is created with the UNIQUE option.
Examples
The following statements create indexes on the EMPLOYEE table:
use test_disk01_persnl
create unique index xempnum on employee (empnum)
create index xempname on employee (last_name, first_name)
The indexes are created on the subvolume PERSNL on the disk volume DISK01 on
the node TEST. The indexes are registered in the NonStop SQL/MP catalog on that
same subvolume.
NonStop ODBC Server Compared With SQL Server
When used through the NonStop ODBC Server, CREATE INDEX differs from the SQL
Server implementation in the following ways:
Feature In SQL Server
In Programs Used With the NonStop
ODBC Server
Can CREATE INDEX
be inside a
transaction?
No Yes
See DDL Statements Allowed in User-Defined
Transactions on page 4-3.
Is auditing of the
volume necessary?
N.A. Yes, the volume on which the index is created
must be audited by TMF.
What locking mode is
used?
Shared The table is locked with a shared table lock
while the index is created.
Maximum number of
indexes that can exist
for a table
250 Follows the rules for NonStop SQL/MP limits.
See information on limits in the NonStop
SQL/MP Reference Manual.