MSSQL

This page describes how to use and configure a connection to Microsoft SQL Server (MSSQL) in Prophecy. MSSQL is a relational database used for storing and querying structured data.

Prerequisites

Prophecy connects to Microsoft SQL Server (MSSQL) 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 MSSQL 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.

Feature	Supported
Read data with a Source gem	Yes
Write data with a Target gem	Yes
Browse data in the Environment browser	Yes
Index tables in the Knowledge Graph	No

Connection parameters

To create a connection with Microsoft SQL Server, enter the following parameters:

Parameter	Description
Connection Name	Name to identify your connection
Server	Address of the server to connect to
Port	Port to use for the connection
Username	Username for your MSSQL Server instance
Password (Secret required)	Password for your MSSQL Server instance

Data type mapping

When Prophecy processes data from Microsoft SQL Server (MSSQL) using SQL warehouses, it converts MSSQL-specific data types to formats compatible with your target warehouse. This table shows how MSSQL data types are transformed for Databricks, BigQuery, and Snowflake.

MSSQL	Databricks	BigQuery	Snowflake
tinyint	`int` Alias: Integer	`int64` Alias: Integer	`number` Alias: Number
smallint	`int` Alias: Integer	`int64` Alias: Integer	`number` Alias: Number
int	`int` Alias: Integer	`int64` Alias: Integer	`number` Alias: Number
bigint	`bigint` Alias: Bigint	`int64` Alias: Integer	`number` Alias: Number
float / real	`double` Alias: Double	`float64` Alias: Float	`float` Alias: Float
decimal	`double` Alias: Double	`float64` Alias: Float	`number` Alias: Number
numeric	`double` Alias: Double	`float64` Alias: Float	`number` Alias: Number
money	`double` Alias: Double	`float64` Alias: Float	`number` Alias: Number
smallmoney	`double` Alias: Double	`float64` Alias: Float	`number` Alias: Number
bit	`boolean` Alias: Boolean	`bool` Alias: Boolean	`boolean` Alias: Boolean
char	`string` Alias: String	`string` Alias: String	`string` Alias: String
varchar	`string` Alias: String	`string` Alias: String	`string` Alias: String
text	`string` Alias: String	`string` Alias: String	`string` Alias: String
nchar	`string` Alias: String	`string` Alias: String	`string` Alias: String
nvarchar	`string` Alias: String	`string` Alias: String	`string` Alias: String
ntext	`string` Alias: String	`string` Alias: String	`string` Alias: String
xml	`string` Alias: String	`string` Alias: String	`string` Alias: String
date	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp
time	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp
datetime	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp
datetime2	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp
smalldatetime	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp
datetimeoffset	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp
rowversion	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp	`timestamp` Alias: Timestamp
binary	`binary` Alias: Binary	`bytes` Alias: Bytes	`binary` Alias: Binary
varbinary	`binary` Alias: Binary	`bytes` Alias: Bytes	`binary` Alias: Binary
image	`binary` Alias: Binary	`bytes` Alias: Bytes	`binary` Alias: Binary
uniqueidentifier	`binary` Alias: Binary	`bytes` Alias: Bytes	`string` Alias: String
sql_variant	`binary` Alias: Binary	`bytes` Alias: Bytes	`string` Alias: String
geometry	`binary` Alias: Binary	`bytes` Alias: Bytes	`binary` Alias: Binary
geography	`binary` Alias: Binary	`bytes` Alias: Bytes	`binary` Alias: Binary
hierarchyid	`binary` Alias: Binary	`bytes` Alias: Bytes	`binary` Alias: Binary

Learn more in Supported data types.

Connections in Prophecy are stored within fabrics, which are assigned to specific teams. Once an MSSQL 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.

Getting started

Build with Agent

Build and inspect pipelines

Explore and visualize

Platform setup

Run and share

Collaboration

Prerequisites

Feature support

Connection parameters

Data type mapping

​Prerequisites

​Feature support

​Connection parameters

​Data type mapping

​Sharing connections within teams

Prerequisites

Feature support

Connection parameters

Data type mapping

Sharing connections within teams