Connect Azure Synapse

1. Create a user for Bigeye

Ask your database administrator to create a bigeye user. This bigeye user has to be able to at the database level. See this for more details.

You can create the user by running the following commands.

For each of these statements, you should make a separate connection to the database.

Connect to master

CREATE LOGIN bigeyeuser WITH PASSWORD = '<password>';
GO;

Connect to the db-to-be-monitored

CREATE USER bigeyeuser FOR LOGIN bigeyeuser;
GO;
ALTER DATABASE [db-to-be-monitored]
--omit the following if already enabled
--query history is required for bigeye table popularity ranking
SET QUERY_STORE = ON;
GRANT SELECT ON sys.query_store_query TO [bigeyeuser];
GRANT SELECT ON sys.query_store_query_text TO [bigeyeuser];
GRANT SELECT ON SCHEMA :: <desired schema for monitoring> TO bigeyeuser;
GO;
--For finer grained control, define SELECT permissions for bigeye service account on desired tables
--example
--GRANT SELECT ON bigeyeTest.stage.orders TO bigeyeuser

2. Whitelist Bigeye IP

Navigate to Firewalls and virtual networks > add client ip. Fill in the Start and End IP using Bigeye’s static IP – 35.163.65.120

3. Gather Synapse connection information

Now gather the following connection information:

Fully qualified server name that hosts the database you want to connect to
For example: bigeye-integration-testing.sql.azuresynapse.net
Name of the database
Authentication method: Username and password

4. Add Synapse as data source in Bigeye

From the Catalog tab in the sidebar, select Add Source. This will take you to a page where you can configure the connection to your database.

To connect a database, you will need to input the following information:

Alias - identifying name for this data source
Vendor - Synapse
Hostname - name of the server that hosts your database
Port - 1433
Database - your database name
Username - username for database
Password - password for database

Once filled out, the form should look something like this

5. Next Steps

Bigeye will now start loading and profiling your tables. It can take up to 24 hours for the profiling to complete and your autometrics/autothresholds to populate. You can now proceed to next steps in the Getting Started guide.