System Requirements
Casabase Cube is a Snowflake Native App and runs within the customer’s Snowflake environment. No separate Casabase Cube OLAP server or locally installed Casabase Cube client is required.
Snowflake Requirements
Section titled “Snowflake Requirements”| Requirement | Details |
|---|---|
| Snowflake Account | A Snowflake account that can obtain and run Snowflake Native Apps. |
| Casabase Cube Listing Access | Access to the Casabase Cube offering through Snowflake Marketplace or a private listing. |
| Installation Privileges | A Snowflake role with sufficient privileges to install and configure the Native App. |
| Application Roles | Users receive Casabase Cube access through CUBE_PUBLIC or CUBE_ADMIN, as appropriate. |
| Required App Privileges | Core functionality uses Native App privileges including READ SESSION and EXECUTE MANAGED TASK. |
| Snowflake Compute | Appropriate Snowflake compute for interactive queries and other workloads that use a warehouse. Warehouse requirements depend on workload and configuration. |
READ SESSION is required for functionality that depends on session context, including Casabase Cube row-level security and Query Builder user context.
EXECUTE MANAGED TASK supports scheduled operations implemented using Snowflake managed tasks.
See Installation for Snowflake Administrators.
Data Requirements
Section titled “Data Requirements”Casabase Cube supports two common starting points.
Creating a Cube from Snowflake Data
Section titled “Creating a Cube from Snowflake Data”Oracle Essbase or Oracle Cloud EPM is not required.
A cube can be created using customer-owned Snowflake data and dimension definition tables.
Casabase Cube requires explicit access to customer-owned source objects that a configured cube reads.
See Creating a Cube from Snowflake Data.
Migrating Oracle Essbase or Oracle Cloud EPM
Section titled “Migrating Oracle Essbase or Oracle Cloud EPM”A typical migration requires:
- The native Essbase outline (
.otl) - A native level-0 export containing the data to migrate
- A Snowflake stage accessible to Casabase Cube for the data import
The outline provides source multidimensional metadata. The native level-0 export provides bottom-level data.
See Oracle Essbase & Cloud EPM Migration and Compatibility Notes.
Browser Requirements
Section titled “Browser Requirements”Casabase Cube is accessed through Snowflake’s web experience.
Use a current web browser supported by Snowflake.
No Casabase-specific browser extension or plugin is required.
Client Software
Section titled “Client Software”No separate Casabase Cube desktop client is required.
Users can work with the application through Snowflake, while programmatic access uses supported Snowflake SQL interfaces, APIs, drivers, and connectors.
Network Requirements
Section titled “Network Requirements”Casabase Cube does not require customers to establish a separate network connection to a Casabase-hosted OLAP service for cube processing.
Users and applications connect to the customer’s Snowflake environment using the organization’s existing Snowflake connectivity and network controls.
Source-Object Access
Section titled “Source-Object Access”Casabase Cube cannot read customer-owned Snowflake tables or stages unless the required access is explicitly granted.
Depending on the workflow, this can include:
USAGEon the applicable database and schemaSELECTon source tablesREADon stages used for migration files
Grant only the objects and privileges required by the configured workload.
Optional Intelligence Requirements
Section titled “Optional Intelligence Requirements”Snowflake Intelligence and Cortex Agent integration has additional Snowflake requirements that are not necessary for core Casabase Cube functionality.
If you plan to enable conversational AI capabilities, see Setting Up the Agent.