Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.prophecy.ai/llms.txt

Use this file to discover all available pages before exploring further.

Prophecy’s Azure Synapse connector supports connecting to dedicated SQL pools that run Microsoft SQL Server (MSSQL). Use this connection instead of the MSSQL connection when you host MSSQL in Azure Synapse dedicated SQL pool. This page describes how to set up the connection.

​
Prerequisites

Prophecy connects to Azure Synapse using the database credentials you provide. These credentials are used to authenticate your session and authorize all data operations during pipeline execution. To use an Azure Synapse connection effectively, your user account must have:
  • SELECT, INSERT, UPDATE, and DELETE on the tables used in your Prophecy pipelines.
  • Access to the database and schema where tables are located.

​
Feature support

The table below outlines whether the connection supports certain Prophecy features.
FeatureSupported
Read data with a Source gemYes
Write data with a Target gemNo
Browse data in the Environment browserYes
Index tables in the Knowledge GraphNo

​
Connection parameters

To create a connection with Azure Synapse, enter the following parameters:
ParameterDescription
Connection NameName to identify your connection
ServerAddress of the server to connect to
PortPort to use for the connection
UsernameUsername for Synapse authentication
DatabaseName of the specific SQL database within your Synapse SQL pool
Password (Secret required)Password for Synapse authentication

​
Sharing connections within teams

Connections in Prophecy are stored within fabrics, which are assigned to specific teams. Once a Synapse connection is added to a fabric, all team members who have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the stored connection credentials.
Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.