Alias name |
- Non-Unicode application limit: 80 bytes
- Unicode-mode application limit: 80 characters
|
Alias table name |
- Non-Unicode application limit: 30 bytes
- Unicode-mode application limit: 30 characters
|
Application name |
- Non-Unicode application limit: 8 bytes
- Unicode-mode application limit: 30 characters
|
Application description |
- Non-Unicode application limit: 79 bytes
- Unicode-mode application limit: 80 characters
|
- Custom-defined function name
- Custom-defined macro name
- Custom-defined function specification
- Custom-defined macro specification
|
- Non-Unicode application limit: 127 bytes. MaxL and the API truncate characters after 127 bytes.
- Unicode-mode application limit: 128 characters. MaxL and the API truncate characters after 128 characters.
In either case, no truncation on server. No error is displayed if truncation occurs. |
Custom-defined function and macro comment |
- Non-Unicode application limit: 255 bytes. After 255 bytes, characters are truncated by MaxL and API.
- Unicode-mode application limit: 256 characters. MaxL and the API truncate characters after 256 characters.
In either case, no truncation on server. No error is displayed if truncation occurs. |
Database name |
- Non-Unicode application limit: 8 bytes
- Unicode-mode application limit: 30 characters
|
Database description |
- Non-Unicode application limit: 79 bytes
- Unicode-mode application limit: 80 characters
|
Directory path
For example: /essbase/bin |
- Non-Unicode application limit: 256 bytes
- Unicode-mode application limit: 1024 bytes
|
File name for calculation scripts, report scripts, or rules files |
- Non-Unicode application limit: 8 bytes
- Unicode-mode application limit: If included within a path, the smaller of the following two values:
- 1024 bytes
- The limit established by the operating system
If not included within a path, as in some MaxL statements, 1024 bytes. |
Filter name |
- Non-Unicode application limit: 30 bytes
- Unicode-mode application limit: 30 characters
|
Group name |
- Non-Unicode application limit: 30 bytes
- Unicode-mode application limit: 30 characters
|
Linked reporting object cell note |
- Non-Unicode application limit: 600 bytes
- Unicode-mode application limit: 600 characters
|
Linked reporting object URL |
512 characters (always single-byte characters) |
Linked reporting object description for URLs and files |
- Non-Unicode application limit: 80 bytes
- Unicode-mode application limit: 80 characters
|
Member comment field |
- Non-Unicode application limit: 255 bytes
- Unicode-mode application limit: 256 characters
|
Member name |
- Non-Unicode application limit: 80 bytes
- Unicode-mode application limit: 80 characters
|
Analytic Server name |
- Non-Unicode application limit: 29 bytes
- Unicode-mode application limit: 50 characters
|
Password |
- Non-Unicode application limit: 100 bytes
- Unicode-mode application limit: 100 characters
|
Substitution variable name |
320 bytes |
Substitution variable value |
256 bytes |
Trigger name |
- Non-Unicode application limit: 30 bytes
- Unicode-mode application limit: 30 characters
|
UDA (user-defined attribute) |
- Non-Unicode application limit: 80 bytes
- Unicode-mode application limit: 80 characters
|
User name |
- Non-Unicode application limit: 30 bytes
- Unicode-mode application limit: 30 characters
|
Caches: data, data file, index |
2 GB |
Calculation script size |
Calculation script text including blanks, tabs, and so on: 64 KB |
Formula size |
- Created in Formula Editor: 64 KB.
- Created in MaxL, using multi-byte characters: 40 KB.
|
Number of aggregate views within an aggregation |
1023 |
Number of security filters |
- Per Analytic Server, 65535
- Per Analytic Services database, 32290
|
Number of users |
30,000. Errors can occur if you create more than 30,000 users. |
Number of members in a block storage outline |
Approximately 1,000,000 explicitly defined in an Analytic Services outline.
Hybrid Analysis and some uses of partitions enable access to many more members than are explicitly listed in an outline, the actual number of members accessible through the database is much higher.
Longer names, such as can occur if multi-byte characters are used, decrease the number of members that are allowed. |
Number of members in an aggregate storage outline |
10,000,000 to 20,000,000 members, depending on available memory and other memory requirements. |
Number of dimension levels in an aggregate storage outline |
The product of the numbers of dimension levels across all dimensions cannot exceed 2 32 which is equal to 4,294,967,296.
For example, to calculate this number for a nine dimension outline with dimension levels 5,10,20,20,20,5,5,5, multiply the number of levels of the first dimension by the number of levels of the second dimension by the number of levels of the third dimension, and so on.
5*10*20*20*20*5*5*5*5 = 1,250,000,000, which is less than 4,294,967,296. |