![]() | |
![]() |
| | Thread Tools | Display Modes |
#21
| |||
| |||
|
|
Hi Ed, Thank you for the update. I'm glad that my point 2 is helpful. Since we can run the query(select into) in Query window to work around the issue, could you please tell me your concern on the work around? Besides, based on my experience, the issue might be by-design. The query can always run successfully in Query window ,but in the View Design mode, timeout expired might happen. The difference with the 2 scenario is the platform the qurey run; and the 2 mode is designed; it is not allowed to change them. Hope the above helpful. Thanks. Best regards, Mark Han Microsoft Online Community Support ================================================== ======= Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com. ================================================== ======= This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ======= |
#22
| |||
| |||
|
|
I have the same problem I'm running SSMS with MS SQL Server 2005. When I try to open view from SSMS interface, from local server (left mouse button on the view?Open view) it shows me “Executing Query” and after 30 seconds write such error: “Error Source: .Net SqlClient Data Provider. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ” When I try execute only select from this view it tooks me about 1min 20 sec and its allright-I see the results. I resolved this problem locally when I changed in registry “SQLQueryTimeout” (HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell\DataProject\SQLQueryTimeout) from 30 sec. to 600 on Server, but only locally now from SSMS I can run Open view and see the execution result. When I run this procedure from remote PC (client) SSMS I see the same problem (“Error Source: .Net SqlClient Data Provider. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ”) Also when I try to run this view from remote PC from MS Access it shows me such error: “ODBC-call failed [Microsoft][ODBC SQL Server Driver]Timeout expired (#0)” I can’t find any solution. |
#23
| |||
| |||
|
|
expired (#0)) |
|
Denny (Denny (AT) discussions (DOT) microsoft.com) writes: I have the same problem I'm running SSMS with MS SQL Server 2005. When I try to open view from SSMS interface, from local server (left mouse button on the view?Open view) it shows me “Executing Query†and after 30 seconds write such error: “Error Source: .Net SqlClient Data Provider. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. †When I try execute only select from this view it tooks me about 1min 20 sec and its allright-I see the results. I resolved this problem locally when I changed in registry “SQLQueryTimeout†(HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell\DataProject\SQLQueryTimeout) from 30 sec. to 600 on Server, but only locally now from SSMS I can run Open view and see the execution result. When I run this procedure from remote PC (client) SSMS I see the same problem (“Error Source: .Net SqlClient Data Provider. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. â€) Also when I try to run this view from remote PC from MS Access it shows me such error: “ODBC-call failed [Microsoft][ODBC SQL Server Driver]Timeout expired (#0)†I can’t find any solution. This query timeout is a client-side setting, so there is no choice but to set it every client you use. You don't have to hack the registryu to address it it SSMS; the setting is exposed under Tools->Option->Designers. Most client APIs have this timeout set to 30, but the query window in Mgmt Studio uses 0 - wait forever. If you don't want to change the timeout everywhere, there is only way out: speed up your view. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
#24
| |||
| |||
|
|
Thanks for reply >>Erland Sommarskog But I have already set - Connection time-out: 600 seconds and Execution timeout:600 seconds. Also in Tools-->Options-->Query Execution: Execution time-out:0 In Designers menu - Transaction time-out: 600 seconds But it also not work I have the same problem - (“Error Source: .Net SqlClient Data Provider. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ”) |
|
And how to solve problem with MS Access (ODBC-call failed [Microsoft][ODBC SQL Server Driver]Timeout expired (#0)) |
#25
| |||
| |||
|
|
Denny (Denny (AT) discussions (DOT) microsoft.com) writes: Thanks for reply >>Erland Sommarskog But I have already set - Connection time-out: 600 seconds and Execution timeout:600 seconds. Also in Tools-->Options-->Query Execution: Execution time-out:0 In Designers menu - Transaction time-out: 600 seconds But it also not work I have the same problem - (“Error Source: .Net SqlClient Data Provider. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. â€) I see now that in your original post that you mentioned an application. In a .Net app, you set the query timeout on either the Connection object or the Command object with the CommandTimeout property. And how to solve problem with MS Access (ODBC-call failed [Microsoft][ODBC SQL Server Driver]Timeout expired (#0)) If you are using ADO, the answer is the same for ADO .Net. If you are using something else, I don't know the answer, and it's more of an Access question. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
#26
| |||
| |||
|
|
I solve the problem with clients with MS Access by increasing the ODBC timeout from 60 (by default) to 300. This can be done by opening the MS Access SQL-Pass-Through query in Design mode and right clicking on the window then accessing the properties. One of the properties is ODBC timeout. But it still not resolve the problem with MS SQL Server Management Studio. I have only MS SQL Management studio on client PC and when I executing a view I have the same problem! Where I can change that query timeout on that client PC in Management Studio? "Erland Sommarskog" wrote: Denny (Denny (AT) discussions (DOT) microsoft.com) writes: Thanks for reply >>Erland Sommarskog But I have already set - Connection time-out: 600 seconds and Execution timeout:600 seconds. Also in Tools-->Options-->Query Execution: Execution time-out:0 In Designers menu - Transaction time-out: 600 seconds But it also not work I have the same problem - (“Error Source: .Net SqlClient Data Provider. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. â€) I see now that in your original post that you mentioned an application. In a .Net app, you set the query timeout on either the Connection object or the Command object with the CommandTimeout property. And how to solve problem with MS Access (ODBC-call failed [Microsoft][ODBC SQL Server Driver]Timeout expired (#0)) If you are using ADO, the answer is the same for ADO .Net. If you are using something else, I don't know the answer, and it's more of an Access question. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
![]() |
| Thread Tools | |
| Display Modes | |
| |