Artifact Limits

Table 21 contains a list of limits that you may encounter when creating or manipulating Integration Services artifacts.

Table 21. Artifacts and Limits

Artifact	Limit for Applications
Names and Related Fields
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
Essbase Server name	Non-Unicode application limit: 29 bytes Unicode-mode application limit: 50 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.
Data source name	46 characters
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: eis/server/bin	Non-Unicode application limit: 256 bytes Unicode-mode application limit: 1024 bytes
File names for calculation scripts, report scripts, and 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 artifact cell note	599 bytes
Linked reporting artifact URL	512 characters (always single-byte characters)
Member comment field	Non-Unicode application limit: 255 bytes Unicode-mode application limit: 256 characters
Member comment field (extended)	8192 bytes
Member name	Non-Unicode application limit: 80 bytes Unicode-mode application limit: 80 characters
OLAP model name	80 characters
OLAP metaoutline name	80 characters
Password	Non-Unicode application limit: 100 bytes Unicode-mode application limit: 100 characters
Substitution variable name	80 bytes
Substitution variable value	255 bytes
Trigger name	30 bytes
User-defined query	No limitations
User names	Non-Unicode application limit: 30 bytes Unicode-mode application limit: 30 characters
Variable names	32 bytes
Data Load and Dimension Building Limits
Data load query	No limitations
Member load query	No limitations
Number of alias tables associated with a metaoutline	9, including the Default alias table
Number of error messages written to a data load or dimension build error log (DATAERRORLIMIT in essbase.cfg)	Default 1000, minimum 1, maximum 65000
Selection and rejection criteria	Number of characters that describe selection and rejection criteria: combination of all criteria limited to 32 KB
Other Limits
Caches: data, data file, index	2 GB
Formula size	Created in Formula Editor: 64 KB. Formulas in calculation scripts are not subject to this limit. Created in MaxL, using multi-byte characters: 40 KB. Formulas in calculation scripts are not subject to these limits.
Number of security filters	Per Essbase Server, 65535 Per Essbase database, 32290
Number of users	30,000. Errors can occur if you create more than 30,000 users.
Number of members in an Essbase outline	Approximately 1,000,000 explicitly defined in an Essbase outline for block storage Approximately 20,000,000 explicitly defined in an Essbase outline for aggregate storage 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, which often occur if multi-byte characters are used, decrease the number of members that are allowed.