FAQ

4min
Questions we get often regarding this connector from our customers we decided to put here.
We guess there haven't been too many questions yet! If you have a question please submit a question, support, or feature request ticket on our support portal.
...
CREATE USER is not supported in master database : Issue with creating a user in the master database
Please see this article as you are most likely attempt to do this in an Azure Synapse Serverless SQL Pool which is not supported by DLH.io anyway. But if you are interested, what you would need to do is create a User database instead of the query trying for a master database, then use can specify, USE <NEW_USER_DATABASE>, then your other commands should work. But again, DLH.io does not support a serverless SQL pool.
Grantor does not have GRANT permission
What Key Differences with Azure Synapse vs Regular SQL Server Databases
Synapse is more of a managed compute engine with separation of storage. In order to be as nimble as possible most standard analytics and data warehouse and data lakehouse functions for storing data are done only in a dedicated pool. There are differences betwen dedicated pools and serverless Synapse.
Other differences are in:
﻿Data Types﻿
Storage
To see the supported data types run this block of code in your dedicated pool database:
JS
SELECT  t.[name], c.[name], c.[system_type_id], c.[user_type_id], y.[is_user_defined], y.[name]
FROM sys.tables  t
JOIN sys.columns c on t.[object_id]    = c.[object_id]
JOIN sys.types   y on c.[user_type_id] = y.[user_type_id]
WHERE y.[name] IN ('geography','geometry','hierarchyid','image','text','ntext','sql_variant','xml')
 AND  y.[is_user_defined] = 1;
SELECT  t.[name], c.[name], c.[system_type_id], c.[user_type_id], y.[is_user_defined], y.[name]
FROM sys.tables  t
JOIN sys.columns c on t.[object_id]    = c.[object_id]
JOIN sys.types   y on c.[user_type_id] = y.[user_type_id]
WHERE y.[name] IN ('geography','geometry','hierarchyid','image','text','ntext','sql_variant','xml')
 AND  y.[is_user_defined] = 1;
﻿
Why do the Synapse target Data Types have Lower Lengths and Reduced Capabilities
Because of the Synapse columnar indexes, etc. concepts of MAX, such as varchar(max) and nvarchar(max) are not currently supported in Synapse Analytics. If attempting to create or change these inconsistencies in your target may occur. See the Azure Synapse Documentation Reference for Data Type remarks. As such, you might see an error such as, has a data type that cannot participate in a columnstore index. The maximum length for varchar is 8000, and nvarchar 4000.
﻿
﻿
﻿
Updated 29 Mar 2025
Did this page help you?
Change Log & Notes
BigQuery (Google)