Serverless SQL Pool error: Query execution failed with error code 16560

Question

Hi,

Is there currently a problem with Synapse serverless SQL pool? Today we aren't able to read large parquet files. Smaller ones are still fine, but one below for example is about 58MB and today returning error below:

	SELECT  
		*  
	FROM  
	OPENROWSET   
	(   BULK 'RAW/Chorus/TRTD/',  
		DATA_SOURCE = 'ExternalDataSourceDataLake',  
		FORMAT = 'Parquet'  
	) AS RESULT  

Statement ID: {1DC4E066-98EE-4093-BABA-0E77BFA3B459} | Query hash: 0x467EC86E99CB3AFE | Distributed request ID: {C20EC4B7-73A4-4E30-A50D-FF43B9AD9CB2}. Total size of data scanned is 1 megabytes, total size of data moved is 1 megabytes, total size of data written is 0 megabytes.
Msg 16560, Level 20, State 0, Line 1
Query execution failed with error code 16560

Thank you.

Regards,
Saifone

Answer 1

Hello @Saifone Nitipavachon ,
Welcome to the Microsoft Q&A and thanks for posting your query.
We apologize for the inconvenience you have encountered here.
The query execution failure could be due to resource constraints. Did you get a chance to re-try it again and see if that helps?

Here are some troubleshooting options:
• Make sure data types of reasonable sizes are used.
• If your query targets Parquet files, consider defining explicit types for string columns because they'll be VARCHAR(8000) by default. Check inferred data types.
• If your query targets CSV files, consider creating statistics.
• To optimize your query, see Performance best practices for serverless SQL pool.

Please refer to this article containing information about how to troubleshoot the most frequent problems with serverless SQL pool in Azure Synapse Analytics. Please let us know if you need further assistance here.

Answer 2

Hi BhargavaGunnam-MSFT,

Many thanks for your response and troubleshooting info. This turned out to be a transient issue which resolved itself after several hours (thankfully it happened in our development environment, not production). Everything is working as expected again now :)

Regards,
Saifone

Answer 3

Confirmed reproducible in my environment. Only happens via SSMS, and doesn't occur in the web interface.

Answer 4

@Nina Reynolds , thank you! This 16560 error is happening on SSMS again today, so I'm running my SQLs from the Synapse workspace in the interim and yes that works fine.