Share via

Microsoft SQL Server database user requirements

  • Article

Important

The Microsoft SQL Server connector is in Public Preview.

This article describes the privileges you must grant to the Microsoft SQL Server database user that you plan to use for ingesting into Azure Databricks.

Databricks recommends that you create a database user that is solely used for Databricks ingestion.

Grant database privileges

The following table lists the privileges that the database user must have, regardless of whether you use change data capture (CDC) or change tracking. It also shows the commands to grant each privilege.

Privileges Commands
Read access to the following system tables and views in the master database:
  • sys.databases
  • sys.schemas
  • sys.tables
  • sys.columns
  • sys.key_constraints
  • sys.foreign_keys
  • sys.check_constraints
  • sys.default_constraints
  • sys.change_tracking_tables
  • sys.change_tracking_databases
  • sys.objects
  • sys.triggers
 Run the following T-SQL commands in the master database:
GRANT SELECT ON object::sys.databases to <database-user>;
GRANT SELECT ON object::sys.schemas to <database-user>;
GRANT SELECT ON object::sys.tables to <database-user>;
GRANT SELECT ON object::sys.columns to <database-user>;
GRANT SELECT ON object::sys.key_constraints to <database-user>;
GRANT SELECT ON object::sys.foreign_keys to <database-user>;
GRANT SELECT ON object::sys.check_constraints to <database-user>;
GRANT SELECT ON object::sys.default_constraints to <database-user>;
GRANT SELECT ON object::sys.change_tracking_tables to <database-user>;
GRANT SELECT ON object::sys.change_tracking_databases to <database-user>;
GRANT SELECT ON object::sys.objects to <database-user>;
GRANT SELECT ON object::sys.views to <database-user>;
Execute permissions on the following system stored procedures in the database that you want to ingest:
  • sp_tables
  • sp_columns_100
  • sp_pkeys
  • sp_statistics_100
 Run the following T-SQL commands in the database that you want to ingest:
USE <database-name>
GRANT EXECUTE ON object::sp_tables to <database-user>;
GRANT EXECUTE ON object::sp_columns_100 to <database-user>;
GRANT EXECUTE ON object::sp_pkeys to <database-user>;
GRANT EXECUTE ON object::sp_statistics_100 to <database-user>;
SELECT on the schemas and tables that you want to ingest. Run the following T-SQL command for each schema and table that you want to ingest:
GRANT SELECT ON object::<table-name\|schema-name> to <database-user>;
SELECT privileges on the following system tables and views in the database that you want to ingest:
  • sys.indexes
  • sys.index_columns
  • sys.columns
  • sys.tables
  • sys.fulltext_index_columns
  • sys.fulltext_indexes
 Run the following T-SQL commands in the database that you want to ingest:
USE <database-name>
GRANT SELECT ON object::sys.indexes to <database-user>;
GRANT SELECT ON object::sys.index_columns to <database-user>;
GRANT SELECT ON object::sys.columns to <database-user>;
GRANT SELECT ON object::sys.tables to <database-user>;
GRANT SELECT ON object::sys.fulltext_index_columns to <database-user>;
GRANT SELECT ON object::sys.fulltext_indexes to <database-user>;

Change data capture (CDC) privilege requirements

If CDC is enabled, additional privileges are required on the DDL support objects. See Enable built-in CDC in Microsoft SQL Server.

Change tracking privilege requirements

If change tracking is enabled, additional privileges are required on the DDL support objects. See Enable change tracking in Microsoft SQL Server.