Connecting

This error occurs when an AAD user tries to connect to the master database, but does not have a user in master. To correct this issue, either specify the SQL Data Warehouse you wish to connect to at connection time or add the user to the master database. See Security overview article for more details.

The server principal "MyUserName" is not able to access the database "master" under the current security context. Cannot open user default database. Login failed. Login failed for user 'MyUserName'. (Microsoft SQL Server, Error: 916)

This error occurs when an AAD user tries to connect to the master database, but does not have a user in master. To correct this issue, either specify the SQL Data Warehouse you wish to connect to at connection time or add the user to the master database. See Security overview article for more details.

CTAIP error

This error can occur when a login has been created on the SQL server master database, but not in the SQL Data Warehouse database. If you encounter this error, take a look at the Security overview article. This article explains how to create a login and user on master, and then how to create a user in the SQL Data Warehouse database.

Blocked by Firewall

Azure SQL databases are protected by server and database level firewalls to ensure only known IP addresses have access to a database. The firewalls are secure by default, which means that you must explicitly enable and IP address or range of addresses before you can connect. To configure your firewall for access, follow the steps in Configure server firewall access for your client IP in the Provisioning instructions.

Manual scripting, using the scripting wizard, or connecting via SSMS is slow, hung, or producing errors

Please make sure that users have been created in the master database. In scripting options, also make sure that the engine edition is set as “Microsoft Azure SQL Data Warehouse Edition” and engine type is “Microsoft Azure SQL Database”.

Polybase

Issue

Resolution

Load fails because of large rows

Currently large row support is not available for Polybase. This means that if your table contains VARCHAR(MAX), NVARCHAR(MAX) or VARBINARY(MAX), External tables cannot be used to load your data. Loading large rows is currently only supported through Azure Data Factory (with BCP), Azure Stream Analytics, SSIS, BCP or the .NET SQLBulkCopy class. PolyBase support for large rows will be added in a future release.

bcp load of table with MAX data type is failing

There is a known issue which requires that VARCHAR(MAX), NVARCHAR(MAX) or VARBINARY(MAX) be placed at the end of the table in some scenarios. Try moving your MAX columns to the end of the table.