Sybase IQ recognizes four types of tables:
Base tables
Local temporary tables
Global temporary tables
Join virtual tables
Base tables are sometimes called main, persistent, or permanent tables because they are a permanent part of the database until you drop them explicitly. They remain in the database over user disconnects, server restart, and recovery. Base tables and the data in them are accessible to all users who have the appropriate permissions. The CREATE TABLE statement shown in the previous example creates a base table.
There are two types of temporary tables, global and local.
You create a global temporary table, using the GLOBAL TEMPORARY option of CREATE TABLE, or by using the Global Temporary Table Creation wizard in Sybase Central. When you create a global temporary table, it exists in the database until it is explicitly removed by a DROP TABLE statement.
A database contains only one definition of a global temporary table, just as it does for a base table. However, each user has a separate instance of the data in a global temporary table. Those rows are visible only to the connection that inserts them. They are deleted when the connection ends, or commits. A given connection inherits the schema of a global temporary table as it exists when the user first refers to the table. Global temporary tables created on a multiplex server are also created on all other multiplex servers. See Using Sybase IQ Multiplex.
To select into a temporary table, use syntax like the following:
SELECT * INTO #TableTemp FROM lineitem WHERE l_discount < 0.5
Sybase strongly recommends that, when writing scripts that SELECT INTO a temporary table, you wrap any select list item that is not a base column in a CAST expression. This guarantees that the temporary table’s column data type is the data type desired.
You declare a local temporary table for your connection only, using the DECLARE LOCAL TEMPORARY TABLE statement. A local temporary table exists until the connection ends or commits, or within a compound statement in which it is declared. The table and its data are completely inaccessible to other users.
An attempt to create a base table or a global temporary table will fail, if a local temporary table of the same name exists on that connection, as the new table cannot be uniquely identified by owner.table.
You can, however, create a local temporary table with the same name as an existing base table or global temporary table. References to the table name access the local temporary table, as local temporary tables are resolved first.
For example, consider the following sequence:
CREATE TABLE t1 (c1 INT); INSERT t1 VALUES (9); DECLARE LOCAL TEMPORARY TABLE t1 (c1 INT); INSERT t1 VALUES (8); SELECT * FROM t1;
The result returned is 8. Any reference to t1 refers to the local temporary table t1 until the local temporary table is dropped by the connection.
See “Versioning of temporary tables” for versioning information on local temporary tables.
You drop a global temporary table just as you would a base table, with the DROP TABLE statement, or with Sybase Central. You cannot drop or alter a global temporary table while other connections are using the table.
Sybase IQ creates tables in your current database. If you are connected to an IQ database, tables are placed as follows:
Type of table |
Permitted placement |
Default placement |
---|---|---|
Permanent |
IQ store, catalog store |
IQ store |
Global temporary |
IQ temporary store, catalog store |
IQ temporary store |
Local temporary |
IQ temporary store or catalog store; only visible to user who creates it |
IQ temporary store |
A Join Virtual Table is a denormalized table that looks like a regular table; it has a name, columns, rows, and indexes. Sybase IQ creates Join Virtual Tables as a result of a CREATE JOIN INDEX for internal processing purposes and deletes them when you do a DROP JOIN INDEX. You cannot create, modify, or delete Join Virtual Tables, but you may see error messages related to them if you try to use or modify them. Sybase suggests that you ignore all Join Virtual Tables.
Servers running in a multiplex cannot create or drop join indexes. For more information, see Using Sybase IQ Multiplex.