|
|
You're in the
sql server replication
group:Transaction Replication, Help!
sql server replication:
I have two SQL Server 2000 servers using Transactional Replication with Push subscription. Once it was set up, the distribution agent kept displaying "the process is running and is waiting for a response from one of backend connections" while the subscriber's transaction log file kept growing from 1GB to 7 GB. I had to stop the distribution agent. Why is the subscriber's transaction log keeping growing during the initialization? What is being added into the subscriber's transaction log file? BTW, I had to increase the Querytimeout from 300 to 2400 for the distribution agent, otherwise it got timed out.
"FYK" schrieb:
[quoted text, click to view] > I have two SQL Server 2000 servers using Transactional Replication with Push > subscription. Once it was set up, the distribution agent kept displaying "the > process is running and is waiting for a response from one of backend > connections" while the subscriber's transaction log file kept growing from > 1GB to 7 GB. I had to stop the distribution agent. Why is the subscriber's > transaction log keeping growing during the initialization? What is being > added into the subscriber's transaction log file? BTW, I had to increase the > Querytimeout from 300 to 2400 for the distribution agent, otherwise it got > timed out. > > Can someone please help me on this? Please supply information about the amount of data, the number of tables in
There are 10 tables, 9 of them have about 1000 rows, 1 table has 35,000 rows. Total amount of data is about 1 GB. Each table has 1 index. [quoted text, click to view] "Christian Donner" wrote:
> "FYK" schrieb: > > I have two SQL Server 2000 servers using Transactional Replication with Push > > subscription. Once it was set up, the distribution agent kept displaying "the > > process is running and is waiting for a response from one of backend > > connections" while the subscriber's transaction log file kept growing from > > 1GB to 7 GB. I had to stop the distribution agent. Why is the subscriber's > > transaction log keeping growing during the initialization? What is being > > added into the subscriber's transaction log file? BTW, I had to increase the > > Querytimeout from 300 to 2400 for the distribution agent, otherwise it got > > timed out. > > > > Can someone please help me on this? > > Please supply information about the amount of data, the number of tables in
Here is more info:
sp_who2 shows two commands running on the database: 1. GHost Cleanup 2. Delete, CPUTime 296906, DiskIO 520032 No blocking is reported in sp_who2. [quoted text, click to view] "FYK" wrote:
> > There are 10 tables, 9 of them have about 1000 rows, 1 table has 35,000 > rows. Total amount of data is about 1 GB. Each table has 1 index. > > "Christian Donner" wrote: > > > "FYK" schrieb: > > > I have two SQL Server 2000 servers using Transactional Replication with Push > > > subscription. Once it was set up, the distribution agent kept displaying "the > > > process is running and is waiting for a response from one of backend > > > connections" while the subscriber's transaction log file kept growing from > > > 1GB to 7 GB. I had to stop the distribution agent. Why is the subscriber's > > > transaction log keeping growing during the initialization? What is being > > > added into the subscriber's transaction log file? BTW, I had to increase the > > > Querytimeout from 300 to 2400 for the distribution agent, otherwise it got > > > timed out. > > > > > > Can someone please help me on this? > > > > Please supply information about the amount of data, the number of tables in
"FYK" schrieb:
[quoted text, click to view] > There are 10 tables, 9 of them have about 1000 rows, 1 table has 35,000 > rows. Total amount of data is about 1 GB. Each table has 1 index. Oops, that's less than nothing! I have no clue about the behaviour of your
Put the subscription database into select into/bulk copy recovery model.
The backend connections message just means that the distribution agent has started a process and has not communicated back with the replication subsystem yet. Setting QueryTimeout to a larger value will prevent the agent from being marked suspect and eventually failing. This could be a normally message. Run profiler for a while to see what is happening in your subscription database. Chances are that at some point in time the process will complete and replication will continue. You will normally get this message if you are deploying large snapshots. -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "FYK" <FYK@discussions.microsoft.com> wrote in message news:5FA5078F-17C7-4ACF-821F-60747811702C@microsoft.com... > > I have two SQL Server 2000 servers using Transactional Replication with > Push > subscription. Once it was set up, the distribution agent kept displaying > "the > process is running and is waiting for a response from one of backend > connections" while the subscriber's transaction log file kept growing from > 1GB to 7 GB. I had to stop the distribution agent. Why is the subscriber's > transaction log keeping growing during the initialization? What is being > added into the subscriber's transaction log file? BTW, I had to increase > the > Querytimeout from 300 to 2400 for the distribution agent, otherwise it got > timed out. > > Can someone please help me on this?
The same error also occurred when I performed transactional replication among
two sql server 2000 databases - twenty two tables were replicated by pushing it to the subscriber. I want to try the recommended solution and need procedures to walk me through "to change querytimeout". Thanks. [quoted text, click to view] "Hilary Cotter" wrote:
> Put the subscription database into select into/bulk copy recovery model. > > The backend connections message just means that the distribution agent has > started a process and has not communicated back with the replication > subsystem yet. Setting QueryTimeout to a larger value will prevent the agent > from being marked suspect and eventually failing. This could be a normally > message. Run profiler for a while to see what is happening in your > subscription database. > > Chances are that at some point in time the process will complete and > replication will continue. You will normally get this message if you are > deploying large snapshots. > > > > -- > Hilary Cotter > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > "FYK" <FYK@discussions.microsoft.com> wrote in message > news:5FA5078F-17C7-4ACF-821F-60747811702C@microsoft.com... > > > > I have two SQL Server 2000 servers using Transactional Replication with > > Push > > subscription. Once it was set up, the distribution agent kept displaying > > "the > > process is running and is waiting for a response from one of backend > > connections" while the subscriber's transaction log file kept growing from > > 1GB to 7 GB. I had to stop the distribution agent. Why is the subscriber's > > transaction log keeping growing during the initialization? What is being > > added into the subscriber's transaction log file? BTW, I had to increase > > the > > Querytimeout from 300 to 2400 for the distribution agent, otherwise it got > > timed out. > > > > Can someone please help me on this? > >
Thank you.
[quoted text, click to view] "Hilary Cotter" wrote:
> Right click on your agent, select agent properties, steps, double click on > the run agent step, in the commands text box go to the end, hit the space > bar and type -QueryTimeOut 600 > > -- > Hilary Cotter > Director of Text Mining and Database Strategy > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. > > This posting is my own and doesn't necessarily represent RelevantNoise's > positions, strategies or opinions. > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > > > "emgeneral" <emgeneral@discussions.microsoft.com> wrote in message > news:9D793F29-592F-451D-9A7A-1BD48EF71869@microsoft.com... > > The same error also occurred when I performed transactional replication > > among > > two sql server 2000 databases - twenty two tables were replicated by > > pushing > > it to the subscriber. I want to try the recommended solution and need > > procedures to walk me through "to change querytimeout". > > > > Thanks. > > > > > > "Hilary Cotter" wrote: > > > >> Put the subscription database into select into/bulk copy recovery model. > >> > >> The backend connections message just means that the distribution agent > >> has > >> started a process and has not communicated back with the replication > >> subsystem yet. Setting QueryTimeout to a larger value will prevent the > >> agent > >> from being marked suspect and eventually failing. This could be a > >> normally > >> message. Run profiler for a while to see what is happening in your > >> subscription database. > >> > >> Chances are that at some point in time the process will complete and > >> replication will continue. You will normally get this message if you are > >> deploying large snapshots. > >> > >> > >> > >> -- > >> Hilary Cotter > >> Looking for a SQL Server replication book? > >> http://www.nwsu.com/0974973602.html > >> > >> Looking for a FAQ on Indexing Services/SQL FTS > >> http://www.indexserverfaq.com > >> > >> "FYK" <FYK@discussions.microsoft.com> wrote in message > >> news:5FA5078F-17C7-4ACF-821F-60747811702C@microsoft.com... > >> > > >> > I have two SQL Server 2000 servers using Transactional Replication with > >> > Push > >> > subscription. Once it was set up, the distribution agent kept > >> > displaying > >> > "the > >> > process is running and is waiting for a response from one of backend > >> > connections" while the subscriber's transaction log file kept growing > >> > from > >> > 1GB to 7 GB. I had to stop the distribution agent. Why is the > >> > subscriber's > >> > transaction log keeping growing during the initialization? What is > >> > being > >> > added into the subscriber's transaction log file? BTW, I had to > >> > increase > >> > the > >> > Querytimeout from 300 to 2400 for the distribution agent, otherwise it > >> > got > >> > timed out. > >> > > >> > Can someone please help me on this? > >> > >> > >> > >
Right click on your agent, select agent properties, steps, double click on
the run agent step, in the commands text box go to the end, hit the space bar and type -QueryTimeOut 600 -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "emgeneral" <emgeneral@discussions.microsoft.com> wrote in message news:9D793F29-592F-451D-9A7A-1BD48EF71869@microsoft.com... > The same error also occurred when I performed transactional replication > among > two sql server 2000 databases - twenty two tables were replicated by > pushing > it to the subscriber. I want to try the recommended solution and need > procedures to walk me through "to change querytimeout". > > Thanks. > > > "Hilary Cotter" wrote: > >> Put the subscription database into select into/bulk copy recovery model. >> >> The backend connections message just means that the distribution agent >> has >> started a process and has not communicated back with the replication >> subsystem yet. Setting QueryTimeout to a larger value will prevent the >> agent >> from being marked suspect and eventually failing. This could be a >> normally >> message. Run profiler for a while to see what is happening in your >> subscription database. >> >> Chances are that at some point in time the process will complete and >> replication will continue. You will normally get this message if you are >> deploying large snapshots. >> >> >> >> -- >> Hilary Cotter >> Looking for a SQL Server replication book? >> http://www.nwsu.com/0974973602.html >> >> Looking for a FAQ on Indexing Services/SQL FTS >> http://www.indexserverfaq.com >> >> "FYK" <FYK@discussions.microsoft.com> wrote in message >> news:5FA5078F-17C7-4ACF-821F-60747811702C@microsoft.com... >> > >> > I have two SQL Server 2000 servers using Transactional Replication with >> > Push >> > subscription. Once it was set up, the distribution agent kept >> > displaying >> > "the >> > process is running and is waiting for a response from one of backend >> > connections" while the subscriber's transaction log file kept growing >> > from >> > 1GB to 7 GB. I had to stop the distribution agent. Why is the >> > subscriber's >> > transaction log keeping growing during the initialization? What is >> > being >> > added into the subscriber's transaction log file? BTW, I had to >> > increase >> > the >> > Querytimeout from 300 to 2400 for the distribution agent, otherwise it >> > got >> > timed out. >> > >> > Can someone please help me on this? >> >> >>
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 |