PreviousSQL Engine Reference (9.1 revision 1) Next

Pervasive ODBC Engine Interface Limits

Show this topic in Library frames

The following table shows the limits or conditions that apply to features of the Pervasive ODBC Engine Interface.

A Pervasive.SQL database may contain four billion objects in any valid combination. The objects are persisted in the data dictionary files.

See also Naming Conventions in Pervasive.SQL Programmer's Guide, which is part of the Pervasive.SQL Software Developer's Kit (SDK).

Table 2-1 Limits/Conditions of Pervasive.SQL Features
Pervasive.SQL Feature
Limit or Condition
Arguments in a parameter list for a stored procedure
300
CHAR column size
8,000 bytes1
Character string literal
A character in the string may be any ANSI character between 1 and 255 decimal.
Columns in a table
1536
Columns allowed in a trigger or stored procedure
300
Column name
See Table 1-1, Identifier Restrictions by Identifier Type, in Advanced Operations Guide
Column size
2 GB
Correlation name
limited by memory
Cursor name
18 bytes
Database name
See Table 1-1, Identifier Restrictions by Identifier Type, in Advanced Operations Guide
Database sessions
limited by memory
Data file path name
64 byes (the maximum length of the data file path name is a combination of Xf$Loc path and the data file path)
Foreign key name
See Table 1-1, Identifier Restrictions by Identifier Type, in Advanced Operations Guide
Group name
See Table 1-1, Identifier Restrictions by Identifier Type, in Advanced Operations Guide
Index name
See Table 1-1, Identifier Restrictions by Identifier Type, in Advanced Operations Guide
Label name
limited by memory
Number of ANDed predicates
300. For example, this statement uses two ANDed predicates:
SELECT * FROM person WHERE First_Name = 'Janis' AND Last_Name = 'Nipart' AND Perm_Street = '1301 K Street NW.'
Parameter name
126 bytes
Password
See Table 1-1, Identifier Restrictions by Identifier Type, in Advanced Operations Guide
Procedure name
See Table 1-1, Identifier Restrictions by Identifier Type, in Advanced Operations Guide
Referential integrity (RI) constraint (for example, Xr$Name)
20 bytes
Representation of single quote
Two consecutive single quotes (``)
Result name
limited by memory
Savepoint name
limited by memory
SELECT list columns in a query
1600
Size of a single term (quoted literal string) in an SQL statement
14,997, excluding null terminator and quotations (15,000 total)
SQL statement length
64 KB
SQL statements per session
limited by memory
Stored procedure size
64 KB
Table name
See Table 1-1, Identifier Restrictions by Identifier Type, in Advanced Operations Guide
Table rows
2 billion
Joined tables per query
limited by memory
Trigger name
See Table 1-1, Identifier Restrictions by Identifier Type, in Advanced Operations Guide
User name
See Table 1-1, Identifier Restrictions by Identifier Type, in Advanced Operations Guide
VARCHAR column size
8,000 bytes1
Variable name
limited by memory
View name
See Table 1-1, Identifier Restrictions by Identifier Type, in Advanced Operations Guide
1 The maximum size of a CHAR or VARCHAR column that may be indexed is 255 bytes


Chapter contents
Publication contents

Prev topic: ODBC Engine Reference
Next topic: Data Source Name Connection String Keywords