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.
| Author |
Topic |
|
acukier
Starting Member
2 Posts |
Posted - 2006-01-04 : 17:11:17
|
| Hi guys. I'm having the following problem. I'm working with two databases in one server and a linked one in a third. I'm having timeouts while running the query from inside my program (.NET 2003). I've done all what I could imagine, from changing the connect timeout of the ADO connection even to 0, to change the remote query timeout in the servers. I've touched any single option I could see using both, sp_configure (actually I've changed remote login timeout an remote query timeout) and changed the connection timeout using the sp_serveroption. The queries are running fine (slow but fine) using the query analyzer so, there're no other errors.Could you help? Please?Thanks a lot |
|
|
Norwich
Posting Yak Master
158 Posts |
Posted - 2006-01-05 : 00:17:04
|
| If the queries are running fine in QA then clearly you don't have an SQL problem.If you want your computer to be faster then throw it out of the window. |
 |
|
|
madhivanan
Premature Yak Congratulator
22864 Posts |
|
|
acukier
Starting Member
2 Posts |
Posted - 2006-01-05 : 08:51:22
|
| Hi chaps.Thank you both. I was thinking on drop my computer through the windonw but I have two problems with this. I'm not living in a very high floor so the final speed is not going to be enough and secondly, I'm using them to feed my family (not with computers but with what I earn using them!!)Talking seriously, I've realized that is not a connection timeout what I got but a command timeout. After the clue Madhivanan gave me, I changed the client using to connect from sqlclien (net specific for SQL) to OLEDB that actually has a command timeout control. Obviously I had to change all the sqlclient parameters and datasets to their oledb ones but it worth. Now is working.Thanks again |
 |
|
|
|
|
|