Microsoft SQL Server

Overview

Stigg’s integration with Microsoft SQL Server allows you to export your product catalog, customer, and subscription data directly to your SQL Server database for custom reporting and analysis.

Stigg’s native data export integrations are included in the Scale plan, and are also available as an optional add-on to the Growth plan. See Stigg’s pricing for more details.

View the full entity schema

See every table and column exported to your destination, organized by entity group.

Setting up the integration

Prerequisites

Your database must allow TCP/IP connections. This applies to on-premises SQL Server, Azure SQL Database, and Azure Synapse.
If the database is protected by a security group or firewall, you’ll need Stigg’s static IP available to complete the first step below: Cloud Hosted (US) 35.192.85.117/32, Cloud Hosted (EU) 104.199.49.149/32. For private-cloud or self-hosted deployments, contact Stigg support for the static egress IP.

Allow access

Create a rule in your security group or firewall settings to whitelist:

Incoming connections to your host and port (usually 1433) from Stigg’s static IP.
Outgoing connections from ports 1024 to 65535 to Stigg’s static IP.

If your database can’t be made reachable via a static IP, you can connect over an SSH tunnel instead. This requires a bastion host that allows inbound SSH from Stigg’s static egress IP, with an SSH user configured using Stigg’s public key, and access from the bastion host’s IP to the database port. Contact Stigg support for the public key.

Create a writer user

Connect to your database and create a dedicated login and user for Stigg:

USE <database>;
CREATE LOGIN <username> WITH PASSWORD = '<password>';
CREATE USER <username> FOR LOGIN <username>;

Grant it permission to create tables in the database:

GRANT CREATE TABLE TO <username>;

If the target schema doesn’t exist yet, also grant permission to create it — it will be created automatically on first sync:

GRANT CREATE SCHEMA TO <username>;

If the schema already exists, grant the user access to it directly instead:

GRANT SELECT, INSERT, UPDATE, DELETE, ALTER ON SCHEMA :: <schema> TO <username>;

Avoid using @, [, ], /, ?, #, ", \, +, spaces, &, :, ;, %, or = in the username or password — these characters can break connection string parsing.

Connect Stigg with SQL Server

In Stigg, navigate to Integrations > Apps > Microsoft SQL Server.Enter the following information in the connection form:

Field	Description
Host	The hostname or IP address of your SQL Server instance
Port	The port SQL Server listens on. Defaults to `1433`.
Database	The name of the target database
Schema	The schema where Stigg will create and sync tables
Username	The SQL Server user Stigg will authenticate as
Password	The password for the SQL Server user

Click Test & connect.

Select entities to export

After entering your connection details, expand the Entities to export section to choose which entity groups to include in the sync. All groups are selected by default.See Exported entities for a description of each group.

Getting started

Developer tools

Governance (Private Beta)

Modeling your pricing in Stigg

Entitlements

Managing customers, subscriptions and contracts

Getting usage data into Stigg

Snap-in widgets

Native integrations

Importing and exporting data

Going live

Workflow automation

Rolling out pricing changes with confidence

Price localization

Managing your account

High-availability and scale

Security & compliance

Overview

View the full entity schema

Setting up the integration

Prerequisites

​Overview

View the full entity schema

​Setting up the integration

​Prerequisites

Overview

Setting up the integration

Prerequisites