Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 Other SQL Server Topics (2005)
 timeout expired on View in SSMS

Author  Topic 

Denny
Starting Member

3 Posts

Posted - 2009-02-12 : 04:29:36
Hi, everybody
Maybe someone will help me with such problem:
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?

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2009-02-12 : 07:43:58
Is your base tables correctly indexed?
Go to Top of Page

Denny
Starting Member

3 Posts

Posted - 2009-02-12 : 10:43:31
Hi,
What did you mean "correctly indexed"?
Please explain me what should be done to index tables of database correctly?
Thanks a lot
quote:
Originally posted by sodeep

Is your base tables correctly indexed?

Go to Top of Page

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2009-02-12 : 11:24:52
Change connection settings to 300 seconds commandtimeout when connecting to server.
Use properties for connection dialog.



E 12°55'05.63"
N 56°04'39.26"
Go to Top of Page

Denny
Starting Member

3 Posts

Posted - 2009-02-13 : 01:54:40
In Connection propertie window 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. ”)

quote:
Originally posted by Peso

Change connection settings to 300 seconds commandtimeout when connecting to server.
Use properties for connection dialog.



E 12°55'05.63"
N 56°04'39.26"


Go to Top of Page

sqluser2009
Starting Member

1 Post

Posted - 2009-04-17 : 18:05:54
I have the same problem.
When I right click and select "Design" or "open view", I got the message timeout expire in less an a minute. If I extra the view and just the select statement,the result set return in less than 2.5 mintes. If I do "select * from view_name;", I got the result set return in less than 2.5 minutes.
It looks like is SSMS problem which has deafult time out less than a minute set when using Design or Open View to connect.
Does anyone have the solution to this problem?
Your help is approaciate. Thanks.
Go to Top of Page
   

- Advertisement -