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(9.6, 69%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENA%3C/text%3E%3C/svg%3E)
Currently receiving this error when trying to operate within a module in our WMS.
-checked timeout session; set to 0
-Tried most recent drivers OBDC 17/18; along with OLE DB driver
Currently running Windows Server 2022 & SQL Server Management Studio 20
Currently receiving this error when trying to operate within a module in our WMS.
The "error" is a simple query timeout, because the query didn't finish in fashion time.
timeout session; set to 0
Which timeout, connection or query timeout?
Optimize your query.
Or increase the timeout.
And if you are only the user, you need to talk to the developer or the vendor of the product.
From the SQL Server side of things, this is all we can say with the information you have provided.
checked timeout session; set to 0
Is the timeout option modified in the server configuration?
You can configure server options to modify the timeout settings in SSMS.
Additionally, timeouts excluding network connection failures can generally be improved by optimizing the query. It is recommended that you use the Profile in SSMS to trace the timeout queries and view the execution process to optimize the query.
Troubleshoot query time-out errors
Regards
Mikey Qiao
If you're satisfied with the answer, don't forget to "Accept it," as this will help others who have similar questions to yours.
Yes the server config has been set to 0
Is the timeout option modified in the server configuration?
Sorry Mikey, but that's the wrong point, that's a server level setting for remote = linked server settings, it's not related to client queries.
Sorry, I got confused; modifying the query timeout requires using advanced options.
sp_configure 'show advanced options'， 1
GO
RECONFIGURE
GO
sp_configure 'query wait'， 2147483647
GO
RECONFIGURE
GO
Mikey, that is even more wrong. If you are going to answer question on behalf of Microsoft, one would like to think that you master the basics.
The error that Nicolas experience is a client-side error*.* By default, most client APIs have a default timeout of 30 seconds. Meaning that if SQL Server has not completed in that time frame, the API sends SQL Server a so-called attention signal to tell SQL Server stop executing the query (pressing the red button in SSMS produces the same signal). The client API then returns an error to an application.
The only way you can address this in SQL Server is to make the query faster, by adding indexes, removing blocking etc. But in the many cases, the only option is to change the client code to permit for longer execution. (The default is a hole in the head in my opinion.)
The query wait parameter you found relates to a more advanced scenario. Say that a query requires a high memory grant for a sort or hashing operation, and this memory is not available. In this case, the query cannot start executing, but has to wait for the memory to be available. query wait controls for how long time it waits. On the top of my head, I don't know the error message if the timeout elapses, but it is more verbose than "Query timeout expired". You can read more about query wait here: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-query-wait-server-configuration-option?view=sql-server-ver16