Periscope Data Documentation

Connecting to Periscope

First Time Connecting

Connection Definitions

Common Connection Errors

Private Network SSH Tunnels

Integrations

Overview

Getting Started

Keyboard Shortcuts

Charts & Dashboards

Chart Overview

Chart Options

Dashboard Overview

Refresh Mechanics

Organizing Charts

Organizing Dashboards

Table-like Charts

Table Overview

Cohort Grids

Pivot Tables

Graph-like Charts

Overview & General Settings

Chart Types and Settings

Mixing Chart Types

Map Charts

Map Chart Overview

Heatmaps

Clusters and Bubbles

Satellite Maps

GeoJSON

Other Charts & Customizations

Pie Charts

Image Charts

Chart Annotations

Site Administration

Adding Users

Removing Users

User Types

User Groups

Two-Factor Authentication

Managing User Permissions

Dashboard Permissions

Site Preferences

Periscope Cache

Caching Strategies

Querying the Periscope Cache

Cross-Database Joins

CSV Upload

Materializing Views

SQL Formatters

Using SQL Formatters

Composing SQL Formatters

Dollars and Percentages

Time Zone Formatters

Date Aggregation

Date Parts

Basic Filters

Custom Filters

Date Range Filters

Aggregation Filter

Adding, Moving, and Hiding Filters

Advanced Filters

Default Filters

Drilldowns

Parent-Child Filters

Matching Filter Values

Time Zone Conversions

Direct Replacement

User Friendly Names

Views

SQL Views

Joining to Views

More SQL Tools

SQL Snippets

Parameterized SQL Snippets

SQL Alerts

Automatic Joins

Sharing and Embedding

Sharing Dashboards Externally

Email Reports

Easy Embedding

Embed API

Embed API Options

Public CSV URL

Slack API

Slack Linking Reports

Data Management

Adding and Deleting Datasource

Spaces: Data-Level Permissions

Improving Query Throughput

Revoking Table Permissions

Salesforce Datasource

SSO Integrations

Overview

Okta

OneLogin

Google Apps

Materialized SQL Views

To view this documentation for the Periscope Classic UI, click here.

SQL Views can be materialized on the Periscope Data Cache. This means that the query must be in Redshift-supported syntax. Once a view has been materialized for the first time, it can be used in a query for results almost immediately. It is important to note that Periscope searches for view names prior to table names when building the query.

Note: Materializing Views is only available with the cache add-on.

Materialization

For a view to materialize the underlying tables must be cached. By default, the Cache Enabled switch is on, and views are materialized automatically. Caching views stores a copy of the view in Periscope, however, if an immediate version of the view is preferred, the switch can be turned off.

After clicking Save, hover over the information dot to check its status.

Materialized views are kept up-to-date in the background to make sure the data is always fresh. Periscope Data refreshes materialized views once every 1-3 hours. Once it's materialized, the info text turns green:

If the info text is yellow, this indicates that the view failed to cache but is going to try again. The query may have timed out or may be waiting on another dependency to be cache. Failing views retry 10 times.

A red info dot indicates that the view failed to materialize.

Keeping Track of SQL Views

The "i" next to the View's name display information such as when the View was last refreshed, when the View was last modified, and how many charts and Views depend on this View.

In the list of all Views, the colored dots will give quick summary statuses. Green checks indicate successfully cached Views, no icons indicate Views that are in the process of caching, and red circles indicate cache failures.

Naming Conventions

In order for a view to successfully materialize, it must follow the same naming conventions described in Redshift's documentation page.