Skip to content

General

Casabase Cube is a cloud-native OLAP engine built natively on Snowflake.

It provides multidimensional modeling, hierarchical aggregation, formulas, security, and analytical querying while taking advantage of Snowflake’s scalability, governance, and security model.

Casabase Cube is designed as a modern alternative to traditional OLAP platforms such as Oracle Essbase and Microsoft Analysis Services.

See What is Casabase Cube? for an introduction to the platform.

Casabase Cube is delivered as a Snowflake Native App and runs within the customer’s Snowflake environment.

There is no separate Casabase Cube OLAP server or external application infrastructure required to execute cube queries.

Conceptually:

Customer Snowflake Account
├── Customer Data
├── Snowflake Compute
└── Casabase Cube Native App
├── Multidimensional Metadata
├── Managed Cube Data
├── Query Engine
├── Formula Engine
├── Security
└── Administration

See Why a Snowflake Native Application? and High-Level Architecture.

Casabase Cube runs inside Snowflake as a Native App.

Cube configuration, application-managed data, query processing, formulas, security evaluation, auditing, and other core application processing remain within the customer’s Snowflake environment.

This architecture eliminates the need to deploy and operate a separate OLAP server.

Does Casabase Cube require separate infrastructure?

Section titled “Does Casabase Cube require separate infrastructure?”

No separate Casabase Cube OLAP infrastructure is required.

Traditional OLAP platforms can require dedicated application servers, databases, services, storage, patching, backups, and operational processes.

Casabase Cube uses Snowflake as the underlying platform for storage and compute.

Organizations continue to manage their normal Snowflake environment, while Casabase Cube provides the application-specific multidimensional capabilities.

Casabase Cube does not move customer data to infrastructure operated by Casabase Software.

When data is loaded into a cube, Casabase Cube manages the resulting cube data within the Native App in the customer’s Snowflake account.

This is different from querying the original customer source table directly on every cube query.

Conceptually:

Customer Source Data
Data Load
Casabase Cube
Native Application
├── Managed Cube Data
└── Multidimensional Metadata
QUERY_CUBE

The customer source objects and the application-managed cube remain separate.

See Data Storage & Boundaries for the complete data model.

Cube data is managed within the Casabase Cube Native App in the customer’s Snowflake account.

Users query the logical cube rather than specifying the physical fact table used by the application.

For example:

CALL CUBE.QUERY_CUBE(
'FINANCE',
'<POV>',
NULL,
NULL
);

Casabase Cube resolves the managed multidimensional structures and cube data required to execute the query.

See Query Architecture.

Does Casabase Software have access to my data?

Section titled “Does Casabase Software have access to my data?”

Installing Casabase Cube does not give Casabase Software or other third parties access to customer data.

The application runs in the customer’s Snowflake environment, and access to customer-owned Snowflake objects must be explicitly granted to the Native App.

For example, a customer may grant the application access to specific source tables or stages required for cube creation or data loading.

Casabase Cube does not automatically receive access to arbitrary objects in the customer’s Snowflake account.

See Roles and Privileges and Data Storage & Boundaries.

Does Casabase Cube make external network calls?

Section titled “Does Casabase Cube make external network calls?”

Core Casabase Cube processing does not require external connections or outbound data transfer.

The application privacy and governance information reports:

data_egress NONE
external_connections NONE
pii_collection NONE
telemetry DISABLED

Cube data, configuration, query processing, and application audit information remain within the customer’s Snowflake environment.

See Compliance and Privacy for additional information about the application’s data-handling posture.

Does Casabase Cube require Oracle Essbase?

Section titled “Does Casabase Cube require Oracle Essbase?”

No.

Casabase Cube is an independent multidimensional engine and does not require Oracle Essbase or Oracle Cloud EPM to operate.

A cube can be created directly from data and metadata in Snowflake using dimension definition tables.

For organizations migrating existing multidimensional applications, Casabase Cube can also use Oracle Essbase or Oracle Cloud EPM artifacts to create the initial model.

Conceptually:

Oracle Essbase / Cloud EPM
Casabase Cube
or
Snowflake Data
Casabase Cube

See Creating a Cube for the supported creation paths.

Can I create a cube directly from Snowflake data?

Section titled “Can I create a cube directly from Snowflake data?”

Yes.

Casabase Cube can create a multidimensional model directly from data and metadata already available in Snowflake.

Dimension structures are defined using dimension definition tables, which describe information such as:

  • Members
  • Parent-child relationships
  • Aggregation behavior
  • Aliases
  • Formulas
  • Other supported member properties

The first dimension creates the cube, and additional dimensions are then added to the model.

See Creating a Cube from Snowflake Data.

Can Casabase Cube migrate an existing Oracle Essbase or Cloud EPM application?

Section titled “Can Casabase Cube migrate an existing Oracle Essbase or Cloud EPM application?”

Yes.

Casabase Cube supports migration workflows for Oracle Essbase and Oracle Cloud EPM.

The multidimensional model is created from the application’s native Essbase outline (.otl), and cube data can be loaded from a native level-0 export.

This allows organizations to preserve their multidimensional model while moving its execution into Snowflake.

See:

Does Casabase Cube pre-aggregate cube data?

Section titled “Does Casabase Cube pre-aggregate cube data?”

No.

Casabase Cube performs multidimensional aggregation and calculation dynamically at query time rather than requiring traditional pre-aggregation or cube calculation processes.

The query engine resolves:

POV
Hierarchy Context
Security Scope
Aggregation
Formulas
Result

This allows changes to query context, hierarchy structures, formulas, and security scope to participate dynamically in result calculation.

See Query Architecture.

No.

Casabase Cube does not require users to write MDX or traditional Essbase report scripts.

Users can query cubes through supported interfaces including:

  • Query Builder
  • SQL
  • Saved Queries
  • Supported integrations

Programmatic cube queries use standard Snowflake SQL to call Casabase Cube procedures.

See Querying Overview.

Can existing Snowflake tools query Casabase Cube?

Section titled “Can existing Snowflake tools query Casabase Cube?”

Yes.

Casabase Cube is designed to work with the broader Snowflake ecosystem.

Depending on the use case, cube results can be consumed through Snowflake-compatible tools and integrations such as business intelligence platforms, analytical applications, and programmatic clients.

See Integration Points and the Integrations documentation.

Casabase Cube builds on Snowflake’s identity, role, and Native App security model and adds application-level row security for multidimensional data.

At a high level:

Snowflake Roles
Application Roles
Casabase Cube Access
Optional Row-Level Security
Permitted Cube Data

Casabase Cube row-level security is opt-in per user.

A user with application access but no active security rules for a cube is unrestricted by Casabase Cube row-level security.

See Access Control and Security Model.

Does Data Classification restrict access to a cube?

Section titled “Does Data Classification restrict access to a cube?”

No.

Data Classification is governance metadata that identifies the sensitivity or business classification of a cube.

Supported classifications include:

PUBLIC
INTERNAL
CONFIDENTIAL
RESTRICTED

Classification does not itself grant, deny, or filter access.

Access is controlled separately through Snowflake roles, Casabase Cube application roles, and row-level security.

See Data Classification.

Yes.

Casabase Cube maintains an application-level audit log for significant administrative and data-access activity.

Audit information can support:

  • Operational troubleshooting
  • Security reviews
  • Governance processes
  • Change investigation
  • Compliance activities

Audit history remains within the customer’s Snowflake environment.

See Audit Log.

Casabase Cube follows the Snowflake Native App application lifecycle.

Application upgrades can deliver new versions of Casabase Cube while preserving customer-specific application state according to the supported upgrade process.

Administrators should validate application health and representative queries after important upgrades.

See Application Upgrades.

What Snowflake editions does Casabase Cube support?

Section titled “What Snowflake editions does Casabase Cube support?”

Casabase Cube is designed to run as a Snowflake Native App.

Specific Snowflake features used by an implementation can have their own Snowflake edition, region, cloud-provider, or account requirements.

Review System Requirements for the current supported environment and prerequisites before installation.

Casabase Cube is distributed through Snowflake, including Snowflake Marketplace and supported private-listing arrangements.

Licensing and commercial terms depend on the applicable Casabase Cube offering and customer agreement.

See How to Get Casabase Cube for acquisition and installation options.

If you are evaluating or installing Casabase Cube for the first time, start with:

For product-specific questions, continue with the other FAQ topics for installation, cubes and dimensions, querying, formulas, security, performance, migration, and support.