|
|
You're in the
sql server replication
group:Query Timeout
sql server replication:
Hi,
I want to increase query timeout value but I don't know how to do this. Please advise me where to change query timeout value. Is it possible to set this for a particular database? Thanks, Soura.
Hi Sounder,
I think we can increase the Timeout for a whole server(all DB's in that Server) Right click on the server name => Select properties => Choose the Connections tab => Increase the query timeout value. (The value is in seconds. Set it to 0 for unlimited time) => Click OK. Regards, Herbert [quoted text, click to view] "SouRa" wrote:
> Hi, > > I want to increase query timeout value but I don't know how to do this. > Please > advise me where to change query timeout value. Is it possible to set this > for a > particular database? > > Thanks, > Soura. >
Hi Herbert,
Thanks for your reply. There is an option in replication job to change the number of attempts to connect subscriber with some specified time interval. We can modify the information. Similarly is there any option to change query time out (in any replication jobs,subscription properties or any where else)? Thanks, Soura. [quoted text, click to view] "Herbert" wrote:
> Hi Sounder, > > I think we can increase the Timeout for a whole server(all DB's in that > Server) > > Right click on the server name => Select properties => Choose the > Connections tab => Increase the query timeout value. (The value is in > seconds. Set it to 0 for unlimited time) => Click OK. > > > Regards, > Herbert > > > "SouRa" wrote: > > > Hi, > > > > I want to increase query timeout value but I don't know how to do this. > > Please > > advise me where to change query timeout value. Is it possible to set this > > for a > > particular database? > > > > Thanks, > > Soura. > >
Hi Sounder,
I think u need to increase the timeout of merge agent..... Open the Replication monitor in that choose the Merge agent => Right-click appropriate publication and select Agent Profiles... => Click the New Profile button to create the new profile with the appropriate QueryTimeout value => Choose the newly created profile. Hope this will help.. Regards, Herbert [quoted text, click to view] "SouRa" wrote:
> Hi Herbert, > > Thanks for your reply. There is an option in replication job to change the > number of attempts to connect subscriber with some specified time interval. > We can modify the information. Similarly is there any option to change query > time out (in any replication jobs,subscription properties or any where else)? > > Thanks, > Soura. > > "Herbert" wrote: > > > Hi Sounder, > > > > I think we can increase the Timeout for a whole server(all DB's in that > > Server) > > > > Right click on the server name => Select properties => Choose the > > Connections tab => Increase the query timeout value. (The value is in > > seconds. Set it to 0 for unlimited time) => Click OK. > > > > > > Regards, > > Herbert > > > > > > "SouRa" wrote: > > > > > Hi, > > > > > > I want to increase query timeout value but I don't know how to do this. > > > Please > > > advise me where to change query timeout value. Is it possible to set this > > > for a > > > particular database? > > > > > > Thanks, > > > Soura. > > >
Hi Herbert,
Thanks for your reply. Actually I getting time out error in my application frequently. So I decided to increase the query time out value. I found a profile High volume server to server profile (in merge agent profiles), any idea about this? Thanks, Soura. [quoted text, click to view] "Herbert" wrote:
> Hi Sounder, > > I think u need to increase the timeout of merge agent..... > > Open the Replication monitor in that choose the Merge agent => Right-click > appropriate publication and select Agent Profiles... => Click the New Profile > button to create the new profile with the appropriate QueryTimeout value => > Choose the newly created profile. > > Hope this will help.. > > Regards, > Herbert > > > "SouRa" wrote: > > > Hi Herbert, > > > > Thanks for your reply. There is an option in replication job to change the > > number of attempts to connect subscriber with some specified time interval. > > We can modify the information. Similarly is there any option to change query > > time out (in any replication jobs,subscription properties or any where else)? > > > > Thanks, > > Soura. > > > > "Herbert" wrote: > > > > > Hi Sounder, > > > > > > I think we can increase the Timeout for a whole server(all DB's in that > > > Server) > > > > > > Right click on the server name => Select properties => Choose the > > > Connections tab => Increase the query timeout value. (The value is in > > > seconds. Set it to 0 for unlimited time) => Click OK. > > > > > > > > > Regards, > > > Herbert > > > > > > > > > "SouRa" wrote: > > > > > > > Hi, > > > > > > > > I want to increase query timeout value but I don't know how to do this. > > > > Please > > > > advise me where to change query timeout value. Is it possible to set this > > > > for a > > > > particular database? > > > > > > > > Thanks, > > > > Soura. > > > >
Hi Sounder,
Since ur getting timeout in application, i think u have to increase the query timeout of Server instead of replication agent. by my previous post step u can set the query timeout of Server. Regards, Herbert [quoted text, click to view] "SouRa" wrote:
> Hi Herbert, > > Thanks for your reply. Actually I getting time out error in my application > frequently. > So I decided to increase the query time out value. I found a profile High > volume server to server profile (in merge agent profiles), any idea about > this? > > Thanks, > Soura. > > "Herbert" wrote: > > > Hi Sounder, > > > > I think u need to increase the timeout of merge agent..... > > > > Open the Replication monitor in that choose the Merge agent => Right-click > > appropriate publication and select Agent Profiles... => Click the New Profile > > button to create the new profile with the appropriate QueryTimeout value => > > Choose the newly created profile. > > > > Hope this will help.. > > > > Regards, > > Herbert > > > > > > "SouRa" wrote: > > > > > Hi Herbert, > > > > > > Thanks for your reply. There is an option in replication job to change the > > > number of attempts to connect subscriber with some specified time interval. > > > We can modify the information. Similarly is there any option to change query > > > time out (in any replication jobs,subscription properties or any where else)? > > > > > > Thanks, > > > Soura. > > > > > > "Herbert" wrote: > > > > > > > Hi Sounder, > > > > > > > > I think we can increase the Timeout for a whole server(all DB's in that > > > > Server) > > > > > > > > Right click on the server name => Select properties => Choose the > > > > Connections tab => Increase the query timeout value. (The value is in > > > > seconds. Set it to 0 for unlimited time) => Click OK. > > > > > > > > > > > > Regards, > > > > Herbert > > > > > > > > > > > > "SouRa" wrote: > > > > > > > > > Hi, > > > > > > > > > > I want to increase query timeout value but I don't know how to do this. > > > > > Please > > > > > advise me where to change query timeout value. Is it possible to set this > > > > > for a > > > > > particular database? > > > > > > > > > > Thanks, > > > > > Soura. > > > > >
SouRa, rather than adjusting the query timeout setting, why dont you try to
figure out why the queries are taking so long? [quoted text, click to view] "SouRa" <SouRa@discussions.microsoft.com> wrote in message news:14E41307-124F-40A1-A1ED-97E4E9DC7B81@microsoft.com... > Hi Herbert, > > Thanks for your reply. Actually I getting time out error in my application > frequently. > So I decided to increase the query time out value. I found a profile High > volume server to server profile (in merge agent profiles), any idea about > this? > > Thanks, > Soura. > > "Herbert" wrote: > >> Hi Sounder, >> >> I think u need to increase the timeout of merge agent..... >> >> Open the Replication monitor in that choose the Merge agent => >> Right-click >> appropriate publication and select Agent Profiles... => Click the New >> Profile >> button to create the new profile with the appropriate QueryTimeout value >> => >> Choose the newly created profile. >> >> Hope this will help.. >> >> Regards, >> Herbert >> >> >> "SouRa" wrote: >> >> > Hi Herbert, >> > >> > Thanks for your reply. There is an option in replication job to change >> > the >> > number of attempts to connect subscriber with some specified time >> > interval. >> > We can modify the information. Similarly is there any option to change >> > query >> > time out (in any replication jobs,subscription properties or any where >> > else)? >> > >> > Thanks, >> > Soura. >> > >> > "Herbert" wrote: >> > >> > > Hi Sounder, >> > > >> > > I think we can increase the Timeout for a whole server(all DB's in >> > > that >> > > Server) >> > > >> > > Right click on the server name => Select properties => Choose the >> > > Connections tab => Increase the query timeout value. (The value is in >> > > seconds. Set it to 0 for unlimited time) => Click OK. >> > > >> > > >> > > Regards, >> > > Herbert >> > > >> > > >> > > "SouRa" wrote: >> > > >> > > > Hi, >> > > > >> > > > I want to increase query timeout value but I don't know how to do >> > > > this. >> > > > Please >> > > > advise me where to change query timeout value. Is it possible to >> > > > set this >> > > > for a >> > > > particular database? >> > > > >> > > > Thanks, >> > > > Soura. >> > > > >> > > >
Soura,
the querytimeout as you seem to be requesting - for all access to the server - is really a client-side setting. Herbert is right that replicationwise we can set this in the agent profile, but as you seem to be requesting more generally, it'll be a property of the command object if you are using ADO / ADO.NET. Usually this doesn't need changing but there are legitimate cases for it. I also concur with Chris - you might want to start by looking to see if you have blocking issues that can be remedied by using NOLOCK or a reporting server or better indexes for optimization etc. Not always appropriate but still worth verifying. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
Hi, We have modified the Merge agent profile to "High end server to server.." After couple of days of this change, we came across a new error message "the process is running and waiting for a response from one of the backend connections", after this message, we noticed the normal error message " ...clean up". Please provide any other areas we may need to review. We "push" the subscription to the Subscriber. All our foreign keys are not enabled for replication. Thanks, Soura [quoted text, click to view] "Paul Ibison" wrote:
> Soura, > the querytimeout as you seem to be requesting - for all access to the > server - is really a client-side setting. Herbert is right that > replicationwise we can set this in the agent profile, but as you seem to be > requesting more generally, it'll be a property of the command object if you > are using ADO / ADO.NET. Usually this doesn't need changing but there are > legitimate cases for it. I also concur with Chris - you might want to start > by looking to see if you have blocking issues that can be remedied by using > NOLOCK or a reporting server or better indexes for optimization etc. Not > always appropriate but still worth verifying. > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com > (recommended sql server 2000 replication book: > http://www.nwsu.com/0974973602p.html) > >
SouRa,
the first error message is not normally anything to be concerned about. I often get this when initializing. In my case it is the application of the indexes that causes this message. Have a loog at the processes and use bdcc inputbuffer to see exactly what is happening during this time. Please could you post up the complete text of the second error message. Cheers, Paul [quoted text, click to view] "SouRa" <SouRa@discussions.microsoft.com> wrote in message news:800312A8-DE48-44DA-9B1C-705323B6EA6E@microsoft.com... > > Hi, > > We have modified the Merge agent profile to "High end server to server.." > > After couple of days of this change, we came across a new error message > "the > process is running and waiting for a response from one of the backend > connections", after this message, we noticed the normal error message " > ..clean up". > > Please provide any other areas we may need to review. > > We "push" the subscription to the Subscriber. All our foreign keys are not > enabled for replication. > > Thanks, > Soura > > "Paul Ibison" wrote: > >> Soura, >> the querytimeout as you seem to be requesting - for all access to the >> server - is really a client-side setting. Herbert is right that >> replicationwise we can set this in the agent profile, but as you seem to >> be >> requesting more generally, it'll be a property of the command object if >> you >> are using ADO / ADO.NET. Usually this doesn't need changing but there are >> legitimate cases for it. I also concur with Chris - you might want to >> start >> by looking to see if you have blocking issues that can be remedied by >> using >> NOLOCK or a reporting server or better indexes for optimization etc. Not >> always appropriate but still worth verifying. >> Cheers, >> Paul Ibison SQL Server MVP, www.replicationanswers.com >> (recommended sql server 2000 replication book: >> http://www.nwsu.com/0974973602p.html) >> >> >>
Hi Paul,
Thanks for your reply. Following is the second error message. 'The merge process could not perform retention-based meta data cleanup in database 'dbname'.' Thanks, Soura [quoted text, click to view] "Paul Ibison" wrote:
> SouRa, > the first error message is not normally anything to be concerned about. I > often get this when initializing. In my case it is the application of the > indexes that causes this message. Have a loog at the processes and use bdcc > inputbuffer to see exactly what is happening during this time. Please could > you post up the complete text of the second error message. > Cheers, > Paul > > "SouRa" <SouRa@discussions.microsoft.com> wrote in message > news:800312A8-DE48-44DA-9B1C-705323B6EA6E@microsoft.com... > > > > Hi, > > > > We have modified the Merge agent profile to "High end server to server.." > > > > After couple of days of this change, we came across a new error message > > "the > > process is running and waiting for a response from one of the backend > > connections", after this message, we noticed the normal error message " > > ..clean up". > > > > Please provide any other areas we may need to review. > > > > We "push" the subscription to the Subscriber. All our foreign keys are not > > enabled for replication. > > > > Thanks, > > Soura > > > > "Paul Ibison" wrote: > > > >> Soura, > >> the querytimeout as you seem to be requesting - for all access to the > >> server - is really a client-side setting. Herbert is right that > >> replicationwise we can set this in the agent profile, but as you seem to > >> be > >> requesting more generally, it'll be a property of the command object if > >> you > >> are using ADO / ADO.NET. Usually this doesn't need changing but there are > >> legitimate cases for it. I also concur with Chris - you might want to > >> start > >> by looking to see if you have blocking issues that can be remedied by > >> using > >> NOLOCK or a reporting server or better indexes for optimization etc. Not > >> always appropriate but still worth verifying. > >> Cheers, > >> Paul Ibison SQL Server MVP, www.replicationanswers.com > >> (recommended sql server 2000 replication book: > >> http://www.nwsu.com/0974973602p.html) > >> > >> > >> > >
Hi ,
I have doubled the query time out in agent profile from 5 minutes to 10 minutes. But, now I am getting the below error messages frequently, 1. The process is running and waiting for a response from one of the backend connections 2. The process could not make a generation at the ‘Publisher’ 3. Initializing 4. Connecting to publisher ‘publisher name’ 5. The process is running and waiting for a response from one of the backend connections 6. The process could not perform retention-based meta data cleanup in database 'database name' Please advise. Thanks, Soura [quoted text, click to view] "SouRa" wrote:
> Hi Paul, > > Thanks for your reply. > > Following is the second error message. > 'The merge process could not perform retention-based meta data cleanup in > database 'dbname'.' > > Thanks, > Soura > > > "Paul Ibison" wrote: > > > SouRa, > > the first error message is not normally anything to be concerned about. I > > often get this when initializing. In my case it is the application of the > > indexes that causes this message. Have a loog at the processes and use bdcc > > inputbuffer to see exactly what is happening during this time. Please could > > you post up the complete text of the second error message. > > Cheers, > > Paul > > > > "SouRa" <SouRa@discussions.microsoft.com> wrote in message > > news:800312A8-DE48-44DA-9B1C-705323B6EA6E@microsoft.com... > > > > > > Hi, > > > > > > We have modified the Merge agent profile to "High end server to server.." > > > > > > After couple of days of this change, we came across a new error message > > > "the > > > process is running and waiting for a response from one of the backend > > > connections", after this message, we noticed the normal error message " > > > ..clean up". > > > > > > Please provide any other areas we may need to review. > > > > > > We "push" the subscription to the Subscriber. All our foreign keys are not > > > enabled for replication. > > > > > > Thanks, > > > Soura > > > > > > "Paul Ibison" wrote: > > > > > >> Soura, > > >> the querytimeout as you seem to be requesting - for all access to the > > >> server - is really a client-side setting. Herbert is right that > > >> replicationwise we can set this in the agent profile, but as you seem to > > >> be > > >> requesting more generally, it'll be a property of the command object if > > >> you > > >> are using ADO / ADO.NET. Usually this doesn't need changing but there are > > >> legitimate cases for it. I also concur with Chris - you might want to > > >> start > > >> by looking to see if you have blocking issues that can be remedied by > > >> using > > >> NOLOCK or a reporting server or better indexes for optimization etc. Not > > >> always appropriate but still worth verifying. > > >> Cheers, > > >> Paul Ibison SQL Server MVP, www.replicationanswers.com > > >> (recommended sql server 2000 replication book: > > >> http://www.nwsu.com/0974973602p.html) > > >> > > >> > > >> > > > >
Hi
After doubling the query timeout in Replication -agent profile, i am getting error message 'The process could not perform retention based meta-data clean up in database 'Databasename' in one of the databases quite often ( i have 50 databases all of them are being Merge replicated) I have reproduced below row count of MSMERGE_CONTENTS, MSSMERGE_TOMBSTONE and MSMERGE_GENHISTORY for last three days. The details given below. Table Name Rowcount 09/16/2005 09/17/2005 09/19/2005 MSMERGE_CONTENTS 27599 25316 24820 MSMERGE_GENHISTORY 14738 14050 14100 MSSMERGE_TOMBSTONE 57764 50026 54186 IN all the database which we are monitoring row count has been decreasing in the above tables. However in this specific database where we have this meta-deta issue, we notice that the table is actually increasing These tables indexed regularly and checkdb on this database has not repored any errors Any specific reason for this increase of row count. Does it provides any other hints Do we need to monitor any other parameters pl advise. Thanks, Soura [quoted text, click to view] "SouRa" wrote:
> Hi , > > I have doubled the query time out in agent profile from 5 minutes to 10 > minutes. > > But, now I am getting the below error messages frequently, > > 1. The process is running and waiting for a response from one of the backend > connections > 2. The process could not make a generation at the ‘Publisher’ > 3. Initializing > 4. Connecting to publisher ‘publisher name’ > 5. The process is running and waiting for a response from one of the > backend > connections > 6. The process could not perform retention-based meta data cleanup in > database > 'database name' > > Please advise. > > Thanks, > Soura > > "SouRa" wrote: > > > Hi Paul, > > > > Thanks for your reply. > > > > Following is the second error message. > > 'The merge process could not perform retention-based meta data cleanup in > > database 'dbname'.' > > > > Thanks, > > Soura > > > > > > "Paul Ibison" wrote: > > > > > SouRa, > > > the first error message is not normally anything to be concerned about. I > > > often get this when initializing. In my case it is the application of the > > > indexes that causes this message. Have a loog at the processes and use bdcc > > > inputbuffer to see exactly what is happening during this time. Please could > > > you post up the complete text of the second error message. > > > Cheers, > > > Paul > > > > > > "SouRa" <SouRa@discussions.microsoft.com> wrote in message > > > news:800312A8-DE48-44DA-9B1C-705323B6EA6E@microsoft.com... > > > > > > > > Hi, > > > > > > > > We have modified the Merge agent profile to "High end server to server.." > > > > > > > > After couple of days of this change, we came across a new error message > > > > "the > > > > process is running and waiting for a response from one of the backend > > > > connections", after this message, we noticed the normal error message " > > > > ..clean up". > > > > > > > > Please provide any other areas we may need to review. > > > > > > > > We "push" the subscription to the Subscriber. All our foreign keys are not > > > > enabled for replication. > > > > > > > > Thanks, > > > > Soura > > > > > > > > "Paul Ibison" wrote: > > > > > > > >> Soura, > > > >> the querytimeout as you seem to be requesting - for all access to the > > > >> server - is really a client-side setting. Herbert is right that > > > >> replicationwise we can set this in the agent profile, but as you seem to > > > >> be > > > >> requesting more generally, it'll be a property of the command object if > > > >> you > > > >> are using ADO / ADO.NET. Usually this doesn't need changing but there are > > > >> legitimate cases for it. I also concur with Chris - you might want to > > > >> start > > > >> by looking to see if you have blocking issues that can be remedied by > > > >> using > > > >> NOLOCK or a reporting server or better indexes for optimization etc. Not > > > >> always appropriate but still worth verifying. > > > >> Cheers, > > > >> Paul Ibison SQL Server MVP, www.replicationanswers.com > > > >> (recommended sql server 2000 replication book: > > > >> http://www.nwsu.com/0974973602p.html) > > > >> > > > >> > > > >> > > > > > >
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |