Table 8-1 lists the limitations on size and number of objects in a Sybase IQ database. In most cases, computer memory and disk drive are more limiting factors.
Item |
Limitation |
---|---|
Database size |
Maximum database size approximates the number of files times the file size on a particular platform, depending on the maximum disk configuration. Refer to your operating system documentation for kernel parameters that affect the maximum number of files. |
Dbspace size |
Raw: No limit – as large as the device allows. Operating system files: 4TB |
Catalog file size |
Maximum is 1TB for all platforms except for Windows systems with FAT 32-file systems, which have a 4GB limit. Windows systems with NTFS support the 1TB maximum. |
Number of columns per table |
Sybase IQ supports up to 45,000 columns in a table. There might be performance penalties with more than 10,000 columns in a table. |
Number of files per database |
Operating system limit that user can adjust; for example, using NOFILE. Typically, 2047 files per database. |
Number of rows per table |
Limited by table size, upper limit 248 |
Number of rows per LOAD TABLE or INSERT statement |
2GB - 1 |
Number of tables per database |
4,293,918,719 |
Number of tables referenced per transaction |
No limit |
Number of tables or views referenced per query |
512 |
Number of tables or views in a single FROM clause |
16 to 64, depending on the query, with join optimizer turned on. |
Number of UNION branches per query |
128. If each branch has multiple tables in the FROM clause, the limit on tables per query reduces the number of UNION branches allowed. |
Table size |
Limited by database size. |
Row size |
Sybase recommends a limit of half the page size. |
Field size |
255 bytes for BINARY, 32,767 bytes for VARBINARY 32,767 for CHAR, VARCHAR Up to 512 TB for 128 KB pages or 1 PB for 512 KB pages for LONG BINARY, LONG VARCHAR |
Maximum length of SQL statement |
Defaults to Catalog page size (not IQ page size) of connected database.This affects long commands such as RESTORE statements with many renamed databases. To run such commands, you may start the server with an increased -gp setting, although the default of -gp 4096 should generally be used. |
Maximum length of variable-length FILLER column |
512 bytes |
Number of indexes |
32,767 per table |
Maximum key size |
255 bytes for single-column index 5300 bytes for multicolumn index |
Number of tables per join index (number of tables that can be joined in one query block) |
32 |
Number of values in an IN list |
250,000 |
Number of stored procedures per database |
2^32 – 1 = 4 294 967 295 |
Number of events per database |
2^31 – 1 = 2 147 483 647 |
IQ page size |
Must be between 64KB and 512KB. |
Maximum number of users (connected and concurrent) |
1000 on 64-bit platforms: AIX, Sun Solaris, and HP 200 on 32-bit platforms: Linux and Windows. |
Maximum size of temp extract file |
Set by TEMP_EXTRACT_SIZEn option. Platform limits are: AIX & HP-UX: 0 - 64GB Sun Solaris: 0 - 512GB Windows: 0 - 128GB Linux: 0 - 512GB |
Sun Solaris OS error initializing raw device Sun Solaris only: When creating a database or dbspace on a raw device in version 12.6 and later releases, Sybase IQ performs a series of calculations to determine the correct size of the raw partition. Each time Sybase IQ tries to initialize the device using its calculation, an operating system error is reported until an appropriate size is calculated. The database or dbspace is successfully created and the errors can be ignored. These errors were not reported in Sybase IQ version 12.5 and earlier releases when creating a database or dbspace on a raw device.