dbTalk Databases Forums  

timeout expired on View

microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools


Discuss timeout expired on View in the microsoft.public.sqlserver.tools forum.



Reply
 
Thread Tools Display Modes
  #21  
Old   
Denny
 
Posts: n/a

Default Re: timeout expired on View - 02-12-2009 , 02:36 AM






Hi, everybody
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.
What shell I do? Any suggestions?


"Mark Han[MSFT]" wrote:

Quote:
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.
================================================== =======



Reply With Quote
  #22  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: timeout expired on View - 02-12-2009 , 05:20 PM






Denny (Denny (AT) discussions (DOT) microsoft.com) writes:
Quote:
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



Reply With Quote
  #23  
Old   
Denny
 
Posts: n/a

Default Re: timeout expired on View - 02-13-2009 , 04:21 AM



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
Quote:
expired (#0))
"Erland Sommarskog" wrote:

Quote:
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



Reply With Quote
  #24  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: timeout expired on View - 02-13-2009 , 03:46 PM



Denny (Denny (AT) discussions (DOT) microsoft.com) writes:
Quote:
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.

Quote:
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



Reply With Quote
  #25  
Old   
Denny
 
Posts: n/a

Default Re: timeout expired on View - 02-17-2009 , 04:08 AM



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:

Quote:
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



Reply With Quote
  #26  
Old   
William Vaughn \(MVP\)
 
Posts: n/a

Default Re: timeout expired on View - 02-17-2009 , 12:02 PM



SSMS| Tools | Options|Query Execution|SQL Server| Query Timeout.

hth

--
__________________________________________________ ________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
__________________________________________________ __________________________________________



"Denny" <Denny (AT) discussions (DOT) microsoft.com> wrote

Quote:
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



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.