Azure Synapse Analytics is an analytics service that combines data warehousing capabilities with Big Data analytics. If offers a unified data engineering platform to ingest, explore, manage, and serve your data for analytics and Business Intelligence. You can query data on your own terms, using either serverless or dedicated computing resources based on your requirements.
RudderStack lets you configure Azure Synapse as a destination to which you can send your event data seamlessly.
To set up an Azure Synapse Analytics user, you will need to have an Azure subscription for the SQL Data Warehouse
In order to send events to Azure Synapse, you will first need to add it as a destination in RudderStack and connect it to your data source. Once the destination is enabled, the tracked source data will automatically start flowing to Azure Synapse via RudderStack.
To configure Azure Synapse as a destination, follow these steps:
Configure your data source in RudderStack if you haven't already.
After choosing a source, click on the Add Destination button and select Azure Synapse from the list of destinations.
Assign a name to your destination and then click on Next. You should then see the following screen:
Enter the following credentials in the Connection Settings:
Host - Enter the host name of your Azure Synapse service.
Database - The database name in your Azure Synapse instance where the data is to be sent goes here.
User - Enter the user name which has the required read/write access to the above database.
Port - Enter the port number associated with the Azure Synapse database instance.
Password - The password for the above user goes here.
SSL Mode - Enter the SSL modes for connecting to your Azure Synapse instance.
Bucket Provider - Select the intermediate storage for storing the staging files. RudderStack currently supports Amazon S3, MinIO, Google Cloud Storage, and Azure Blob Storage.
There are some limitations when it comes to using reserved words in a schema, table, or column names. If such words are used as event names, traits or properties, they will be prefixed with a
_ when RudderStack creates tables or columns for them in your schema.
Also, note that integers are not allowed at the start of the schema or table name. Hence, RudderStack prefixes such schema, column or table names with a
'25dollarpurchase' will be changed by RudderStack to
RudderStack converts the event keys into lower case before exporting the data into Azure Synapse, so that it does not create two tables if the event name has two different cases.