ODBC Server Reference Manual

Transact-SQL Language
HP NonStop ODBC Server Reference Manual—429151-002
4-70
Dropping Partitioned Tables
When you drop a table using the NonStop ODBC Server, NonStop SQL/MP drops the
table and all dependent views and indexes. The NonStop ODBC Server, however,
does not clear the mapping table entries for the views or indexes.
The only way to clear the mapping table entries in this situation is to run the catalog
utility statement REFRESH.
For information on REFRESH, see Maintaining Catalogs on page 7-27.
Dropping Partitioned Tables
NonStop SQL/MP allows creation of partitioned tables. Each partition has an entry in
the mapping table. Dropping a table that is partitioned causes all the partitions to be
dropped, but the mapping entries will remain. To clear the entries, run the catalog utility
statement REFRESH.
For information on REFRESH, see Maintaining Catalogs on page 7-27.
NonStop ODBC Server Compared With SQL Server
When used through the NonStop ODBC Server, DROP TABLE differs from the SQL
Server implementation in the following ways:
Note. When the mapping table entries are not cleared and you later attempt to create a view
or index by the same name, you will receive error messages saying that the object already
exists when in fact it does not.
Feature In SQL Server
In Programs Used With the
NonStop ODBC Server
Can DROP TABLE be
inside a transaction?
No Yes, if the table is audited.
Must partitions be
available?
N.A. Yes, and although all partitions are
dropped, mapping entries for them
are not. See Dropping Partitioned
Tables.
Are dependent programs
automatically invalidated?
N.A. Yes