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

CSV Download

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

Connecting to a SQL Server Database

Prior to connecting the SQL Server Database, follow the platform specific instructions on whitelisting Periscope's IPs.

To connect to a SQL Server database, please ensure that Periscope can talk to the database over TCP. Periscope will check that the port is accessible through the firewall, that it responds to TCP, that Periscope can login, and that the server is accessible from Periscope.

These steps are modeled after Microsoft Azure's SQL Server guide, which offers even more information about securely connecting to a SQL Server database.

Open TCP ports in the Windows firewall

  1. Open Windows firewall from the start menu
  2. In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then click New Rule in the action pane.

  3. In the New Inbound Rule Wizard dialog box, under Rule Type, select Port, and then click Next.

  4. In the Protocol and Ports dialog, use the default TCP. In the Specific local ports box, type the port number of the Database Engine (1433 for the default).
  5. Click Next.
  6. In the Action dialog box, select Allow the connection, and then click Next.
  7. In the Profile dialog box, select Public, Private, and Domain. Then click Next.
  8. In the Name dialog box, type a name and description for this rule, and then click Finish.

Configure SQL Server to listen on the TCP protocol

  1. While connected to the virtual machine, on the Start page, type SQL Server Configuration Manager and hit ENTER.
  2. In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration.
  3. In the console pane, click Protocols for MSSQLSERVER (the default instance name.) In the details pane, right-click TCP, it should be Enabled for the gallery images by default. For custom images, click Enable (if its status is Disabled.)
  4. In the console pane, click SQL Server Services. In the details pane, right-click SQL Server (instance name) (the default instance is SQL Server (MSSQLSERVER)), and then click Restart, to stop and restart the instance of SQL Server.

Create SQL Server authentication logins

To connect to the Database Engine from another computer, create at least one SQL Server authentication login.

  1. In SQL Server Management Studio Object Explorer, expand the folder of the server instance where the new login will be created.
  2. Right-click the Security folder, point to New, and select Login....
  3. In the Login - New dialog box, on the General page, enter the name of the new user in the Login name box.

  4. Select SQL Server authentication.

  5. In the Password box, enter a password for the new user. Enter that password again into the Confirm Password box.
  6. To enforce password policy options for complexity and enforcement, select Enforce password policy (recommended). This is a default option when SQL Server authentication is selected.
  7. From the Default database list, select a default database for the login. master is the default for this option. If a user database has not yet been created, leave this set to master.
  8. Click OK.

Configure SQL Server for mixed mode authentication

The SQL Server Database Engine cannot use Windows Authentication without domain environment. To connect to the Database Engine from Periscope, configure SQL Server for mixed mode authentication. Mixed mode authentication allows both SQL Server Authentication and Windows Authentication.

  1. In SQL Server Management Studio Object Explorer, right-click the name of the instance of SQL Server (the virtual machine name), and then click Properties.
  2. On the Security page, under Server authentication, select SQL Server and Windows Authentication mode, and then click OK.

  3. In Object Explorer, right-click the server, and then click Restart. (If SQL Server Agent is running, it must also be restarted.)

    Finally, follow the instructions on granting table permissions so that Periscope can query the tables.