FAQ

questions we get often regarding this connector from our customers we decided to put here if you have any questions that aren't listed here, please submit a question, support, or feature request ticket on our https //support datalakehouse io create user is not supported in master database issue with creating a user in the master database please see https //learn microsoft com/en us/azure/synapse analytics/sql/resources self help sql on demand?tabs=x80070002#create statement isnt supported in the master database 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 https //learn microsoft com/en us/azure/synapse analytics/sql data warehouse/sql data warehouse tables data types#unsupported data types storage to see the supported data types run this block of code in your dedicated pool database 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 https //learn microsoft com/en us/sql/t sql/data types/nchar and nvarchar transact sql?view=azure sqldw latest\&preserve view=true#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