| Author |
Topic |
|
juicyapple
Posting Yak Master
176 Posts |
 Posted - 2008-02-11 : 02:35:47
|
| Hi, I am doing insert data from table A to B but I get this error message. Does this because of the insufficient disk space problem? I have checked on it, the disk space is still more than enough...Please advise.OLE DB provider "SQLNCLI" for linked server "SERVER5" returned message "Query timeout expired". Msg 7399, Level 16, State 1, Line 1 The OLE DB provider "SQLNCLI" for linked server "SERVER5" reported an error. Execution terminated by the provider because a resource limit was reached. Msg 7421, Level 16, State 2, Line 1 Cannot fetch the rowset from OLE DB provider "SQLNCLI" for linked server "SERVER5". . Thanks. |
|
|
tprupsis
Yak Posting Veteran
88 Posts |
Posted - 2008-02-11 : 11:55:18
|
| I wouldn't think this is related to disk space. What database are you linking to? |
 |
|
|
juicyapple
Posting Yak Master
176 Posts |
Posted - 2008-02-11 : 21:19:56
|
| I am executing a store procedure in SERVER1, which performs insert data from SERVER2.tableA to SERVER2.tableB, and the tableA consists of ~50000000 rows data. Any idea? |
|
|
|
tprupsis
Yak Posting Veteran
88 Posts |
Posted - 2008-02-12 : 01:35:03
|
| Your error message refers to SERVER5, but you only mention SERVER1 and SERVER2. What version of SQL Server are you using? In SQL 2005, look at your server properties in SQL Server Management Studio. On the Connections page, there is a timeout value for remote queries. On my local SQL Express instance, this is defaulted to 600 seconds. You might try increasing that if your query of 50M records runs longer than that. |
|
|
|
juicyapple
Posting Yak Master
176 Posts |
Posted - 2008-02-12 : 02:21:24
|
| Your error message refers to SERVER5, but you only mention SERVER1 and SERVER2. What version of SQL Server are you using? Sorry, should be like this,1.In SERVER1 SQL 2005, executing store procedure to insert data from linked server SERVER5.tableA to SERVER5.tableB. 2.SERVER 5 is using SQL 2K.On the Connections page, there is a timeout value for remote queries. On my local SQL Express instance, this is defaulted to 600 seconds. You might try increasing that if your query of 50M records runs longer than that.SERVER1 uses the default remote query timeout = 600 seconds.If I increase the timeout value, it also affects all the applications connected to the database? |
|
|
|
tprupsis
Yak Posting Veteran
88 Posts |
Posted - 2008-02-12 : 11:12:55
|
| Yes, that setting should impact anything sending a remote query to the server. I think you'll need to adjust the default remote query timeout on SERVER5 though, not on SERVER1. I would assume Enterprise Manager has a similar setting, but I couldn't tell you where to find it.There's also a Query Timeout setting in your linked server properties. That defaults to 0, which uses the remote server's default. If you need to increase the timeout for just queries issued through the linked server, you might try adjusting that property instead. |
|
|
|
juicyapple
Posting Yak Master
176 Posts |
Posted - 2008-02-12 : 20:14:55
|
| I do not want to change the default remote query timeout as this may affect others application. If I increase only the timeout value through a linked server properties, means it is only applicable to all queries through linked server? |
|
|
|
Rina
Starting Member
2 Posts |
Posted - 2009-08-05 : 03:21:18
|
| Hi I get this error "Query timeout expired" Description: "Query timeout expired" Help File: "(null)" Help Context: 0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}OLE DB Error Records for hr = 0x80040e31" Could you tell me what is wrong? I get this error at my local machine .Im using the sql2005 ExpressThanks |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
|
|
CLS
Starting Member
1 Post |
Posted - 2010-05-10 : 02:54:21
|
| @tprupsis had answered the question.If you connect to an SQL server, you can specify query timeout.If you connect to a linked server from an another connection, the destination server specifies the query timeout.This can be changed with SQL Server Management Studio, connect to the destination server as "sa", right click the server, click "Properties", go to the "Connections" page set "Remote query timeout". |
|
|
|
|
Query timeout expired