This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 62%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENC%3C/text%3E%3C/svg%3E)
Created .net core console application inside using ADO drivers and synapse serverless(on-demand sql) connection string to executing csv to parquet conversion script.
Small set of data it's working fine. But when medium set of data we are getting timeout exception in 30 seconds and getting below error.
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
We increased the Connection Timeout=3000 in connection string but still we are getting timeout exception in 30 seconds.
Is there any way we can increase the script execution time in synapse serverless side or any ware?
Could you pleas help me how to resolve this issue?
completion of the operation ... We increased the Connection Timeout
You get a Command timeout, not a connection timeout
Hi
Thanks for the reply. I used commandtimeout property and increased the time. How much time i increase, still command is terminating in 30 seconds. But this time i'm getting different error like
"A transport-level error has occured when receiving results from the server. (provider: Tcp Provider, error:0 - The specified network name is no longer available.)
Could you please help.
What happens if you run the query from SSMS or Azure Data Studio? They should wait forever.
My interpretation of that error message is that the network connection got lost, but it's a little intriguing if happens exactly after 30 seconds.
Yes the query is running fine in both SSMS and Azure Data Studio, able to create external tables and parquet files. There is no exception also. But when im triggering this query from .net core application using ADO drivers and synapse serverless connection string. I'm getting timeout exception.
I'm getting timeout exception.
But the timeout exception has been sorted out, hasn't it? Instead you are getting this different error, which sounds mysterious to me. Not that I have ever worked with Synapse Serverless, but I can't see that this would be different from regular engine.
Well, since it's serverless, you will have to account for a warming-up time if the pool is stopped. But I would expect that to matter more in the connection step than when running the query.
We resolved the issue.
For timeout exception we need to add command timeout.
if your getting "A transport-level error has occurred when receiving results from the srever.(provider:TCP provider, error:0 - The specified network name is no longer available.) error. You need to add connect.ClearAllPools().
This error will come only when your testing your code on local. when your moving your code in prod environment you can remove ClearAllPools.
Finally the code like below
public void Exs(string connection,string sql)
{
SqlConnection conn=null;
try {
SqlConnection.ClearAllPools();
using(conn=new SqlConnection(connection))
{
conn.Open();
using(SqlCommnad cmd=new SqlCommnad(sql,conn))
{
cmd.CommandTimeout=0;
var output=cmd.ExecuteNonQuery();
}
conn.Close();
}
}
catch(Exception e)
{
throw;
}
}
Great to hear that you got it sorted out!
I would suggest that you convert your comment to an Answer and then accept that for the benefit of others who find this thread. (Use the More menu to find command to convert to Answer.)