GoodData-Azure Synapse Analytics Integration Details

When setting up direct data distribution from your Microsoft Azure Synapse Analytics, pay attention to the considerations and best practices listed in this article.

This article is applicable to all use cases of GoodData and Azure Synapse Analytics integration:

Required Components

Azure Synapse Analytics must have a Logical Data Warehouse layer.

Ports Used

You can use any port from within the range of 1024-65535.

User Access Rights

We recommend that you grant the following minimum access rights to the user who is referenced in Data Sources:

GRANT SELECT ON SCHEMA {database_name}.{schema_name} TO {user_name} WITH GRANT OPTION;

Database Permissions

Configure your Azure Synapse Analytics to have sufficient permissions to be able to establish outbound connections.

Access to Azure Synapse Analytics

So that the GoodData platform can connect to your Azure Synapse Analytics, authorize access to it. For information, see GoodData IP Addresses and IP Whitelisting.

Active Directory

If you use Active Directory for user authentication, make sure that the parameters in Active Directory are aligned with the GoodData platform.

Data Types

Azure Synapse Analytics provides a wide range of data types. During mapping the SQL schema and the GoodData logical data model (LDM), data types are automatically converted from an Azure Synapse Analytics data type to a GoodData LDM data type. Some columns may be ignored because their data type is not supported within GoodData or their type may lead to performance issues. If you want to prevent automatic changes, update the schema manually.

Azure Synapse Analytics Data TypeGoodData LDM Data Type
bigintBIGINT
bitBOOLEAN
charVARCHAR
dateDATE
datetimeDATE
datetime2DATE
decimalNUMERIC
floatFLOAT
intINTEGER
moneyNUMERIC
ncharVARCHAR
numericNUMERIC
nvarcharVARCHAR
realFLOAT
smalldatetimeDATE
smallintINTEGER
smallmoneyNUMERIC
tinyintINTEGER
uniqueidentifierVARCHAR
varcharVARCHAR
Other data typesNot supported

Custom Parameters

Custom parameters in URLs are not supported.