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

Query Management

Color Themes

Dashboard Refresh Management

Usage Data

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

Version History

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

Schema Browser

SSO Integrations

Overview

Okta

OneLogin

Google Apps

Querying the Periscope Cache

Queries automatically run on the Periscope Cache if the underlying tables are cached and the SQL is Redshift-compatible. If the query fails on the Cache, Periscope Data will run it directly against the source database.

The database that the query is running against can be determined by hovering over the info icon in the chart editor. A green dot indicates that the query was run on the cache, while a red dot indicates that the query ran directly on the source database.

Note: This functionality is only available with the cache add-on.

Forcing a Query to Run on the Cache

To ensure that the query doesn't fall back to the source database, add --yes_cache or -- --yes_cache (for MySQL) to the top of the query.

For example, if a chart using a view called panthers_stats is showing an error about a nonexistent column, it may be falling back to the source database and giving an unhelpful error message.

Adding --yes_cache to the top of the query ensures that it doesn't fall back to the source database, where panthers_stats doesn't exist.

Now the chart shows a more relevant error.

Forcing a Query to Run on the Source Database

To run queries against the source database directly, there is a similar syntax. Add --no_cache or -- --no_cache (for MySQL) to the top of a query to skip the Periscope Cache.