Microsoft SQL Server

Add SQL Server as a decube connection and help your team discover, document and monitor their data assets to drive data-driven insights and decisions.

You can also use this document to connect Azure SQL Server to Decube.

Supported Capabilities

Capability	Supported
Metadata Extraction	✅
Metadata Types Collected	Schema, Table, Column
Data Profiling	✅
Data Preview	✅
Data Quality	✅
Configurable Collection	❌
External Table	❌
View Table	❌
Stored Procedure	❌

Data Quality Support

Capability	Supported
Freshness	✅
Volume	✅
Field Health	✅
Custom SQL	✅
Schema Drift	✅
Job Failure	❌

Lineage Support

Capability	Supported
View Table Lineage	❌
External Table Lineage	❌
SQL Query Lineage	❌
Foreign Key Lineage	✅
Stored Procedure Lineage	❌

Connection Requirements

Connecting to decube is as easy as providing us with credentials to your Microsoft SQL database. At a minimum, we require

• username

• password

• host address

• host port

• database name

Microsoft SQL Server

The source name will be for you to differentiate and recognize particular sources within the decube application.

We strongly encourage you to create a decube read-only user for this credential purpose, which you can follow here.

Security Concerns

If access to your database is protected by security measures, we allow for connecting via SSH Tunneling or you could whitelist our IP. See more here.

Custom User for decube

A custom user would allow for a granular configuration of the user on your database and your connection to decube.

1. Create a New User for decube

CREATE LOGIN [decube] WITH PASSWORD=N'your_password';

1. Execute the following SQL statement to create a new database user and map it to the login created in the previous step

USE your_db_name;
CREATE USER [decube] FOR LOGIN [decube];

1. Add the user to role db_datareader

EXEC sp_addrolemember N'db_datareader', N'decube'