SQL Server
This page describes how to configure SQL Server credentials for use by Census and why those permissions are needed.
🔑 Permissions
These instructions are well tested to connect Census to SQL Server. If you're running into connection issues or missing tables or views, please confirm you've run all of these instructions.
Census reads data from one or more tables (possibly across different schemata) in your database and publishes it to the corresponding objects in destination tools.
We recommend you create a dedicated CENSUS
user account with a strong, unique password. Census uses this account to connect to your SQL Server database. In order for the Census connection to work correctly, the CENSUS
account needs a number of permissions
Required Permissions
These permissions are required for both Basic and Advanced sync engines. They give Census read-only access to any tables and views in any schemata that you would like Census to publish to your service destinations.
SQL Server permissions are complex and there are many ways to configure access for Census. The script below has been tested with recent SQL Server versions and is known to work correctly:
Important: all SQL Server Commands will run within the Database that is specified when running the script
Advanced Sync Engine Permissions
To enable Advanced Sync engine, Census requires additional permissions to enable state tracking within your warehouse.
Advanced Network Configuration
Census can successfully connect to SQL Server instances that are using advanced networking controls including region constraints, IP address allow lists, or SSH Tunneling. For more information, see our Network Access Controls documentation.
Need help connecting to SQL Server?
Contact us via support@getcensus.com or start a conversation with us via the in-app chat.
Last updated