Configuring AtScale
- Viewing and Updating Licenses
- Adding Data Warehouses
- Engine Level Configuration Settings
Managing AtScale
- Managing User Access and Security
  - Connecting to an LDAP Server
  - Configuring Kerberos
- Managing Git
  - About Git Integration
  - Managing Git Repositories in AtScale
- Managing AtScale APIs
  - Accessing the AtScale API
  - AtScale OpenAPI
- Managing Aggregates
  - Aggregate Data Security
  - Working With Aggregate Partitions
  - Dimensionally Modified Aggregates
  - Inbound SQL Hints to Control the Use and Generation of Aggregate Tables
  - Inbound SQL Session Parameters
- Monitoring Queries
  - Using the Queries Page
Working with Data Models
- AtScale Model Design Concepts

Connecting to AtScale From Business-Intelligence Software
- BI Tool Connection Support
- Getting Model Connection Information

Loading search results...

Working with Data ModelsDeploying CatalogsWhat Does Deploying a Catalog Do?

What Does Deploying a Catalog Do?

When you deploy a catalog in AtScale, all of its the models and perspectives become available for queries. After a model is deployed, it can be accessed by your business intelligence (BI) client applications.

Deploying a catalog also starts the build process for user-defined aggregate tables (if they exist). Queries can still be served while aggregate tables are in the process of building. If a catalog does not contain user-defined aggregates, then aggregate tables are not built until AtScale starts receiving queries against a deployed model.