|
|
You're in the
sql server replication
group:Replication failed when destination tabel is using by runnable pro
sql server replication:
my sql server has sp4 installed. i have two databases, D1 and D2. And the transaction replication copys table D1.T1 to D2.T1 at 1:00pm everyday. the problem is: when some applications are continuously using table D2.T1, i mean those processes are in runnable status. And then the replication starts and try to copy data from D1.T1 to D2.T1, it will fail. is there a way to work around this without having to kill those running
btw, the server is running as a publisher, distributor and subscriber.
Database D1 and D2 are hosted on same server. The subscription type is a pull subscription. [quoted text, click to view] "ericsson" wrote:
> hi all, > > my sql server has sp4 installed. i have two databases, D1 and D2. And the > transaction replication copys table D1.T1 to D2.T1 at 1:00pm everyday. > > the problem is: > when some applications are continuously using table D2.T1, i mean those > processes are in runnable status. And then the replication starts and try to > copy data from D1.T1 to D2.T1, it will fail. > > is there a way to work around this without having to kill those running
You have two options. You can run the distribution agent continually to
minimize the impact occurring at 1:00 pm, or you can schedule it to stop around 12:50 pm and restart when the other processes are complete. -- 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] "ericsson" <ericsson@discussions.microsoft.com> wrote in message news:827E13A7-26C0-4C0F-BC2B-D9DC48E34819@microsoft.com... > hi all, > > my sql server has sp4 installed. i have two databases, D1 and D2. And the > transaction replication copys table D1.T1 to D2.T1 at 1:00pm everyday. > > the problem is: > when some applications are continuously using table D2.T1, i mean those > processes are in runnable status. And then the replication starts and try > to > copy data from D1.T1 to D2.T1, it will fail. > > is there a way to work around this without having to kill those running > process which are using table D2.T1 at that time?
Hi Hilary,
Thank you for your information. i understand your words as: deliver transactions only when no other processes are using table D2.T1, or using continually transaction delivery, right? Actually, it had been working perfectly with same configuration before i upgraded the server from sp3 to sp4. Did anything related to replication be changed in sp4? [quoted text, click to view] "Hilary Cotter" wrote:
> You have two options. You can run the distribution agent continually to > minimize the impact occurring at 1:00 pm, or you can schedule it to stop > around 12:50 pm and restart when the other processes are complete. > > -- > 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 > > > > "ericsson" <ericsson@discussions.microsoft.com> wrote in message > news:827E13A7-26C0-4C0F-BC2B-D9DC48E34819@microsoft.com... > > hi all, > > > > my sql server has sp4 installed. i have two databases, D1 and D2. And the > > transaction replication copys table D1.T1 to D2.T1 at 1:00pm everyday. > > > > the problem is: > > when some applications are continuously using table D2.T1, i mean those > > processes are in runnable status. And then the replication starts and try > > to > > copy data from D1.T1 to D2.T1, it will fail. > > > > is there a way to work around this without having to kill those running > > process which are using table D2.T1 at that time? > >
Maybe you are right. I'll check it. Anyway, i'd like to know if transactions
can be delivered to a table which is BEING USED by applications simultaneity. [quoted text, click to view] "Hilary Cotter" wrote:
> There were bug fixes, but none which has caused (AFAIK) this problem on > other systems. Perhaps you have another process running on your system at > 1:00 am which is causing extra load on your system and the overall > degradation is causing this problem to occur. > > -- > 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 > > > > "ericsson" <ericsson@discussions.microsoft.com> wrote in message > news:875E8A04-90D5-44E2-A13B-111C2E8CC143@microsoft.com... > > Hi Hilary, > > > > Thank you for your information. i understand your words as: deliver > > transactions only when no other processes are using table D2.T1, or using > > continually transaction delivery, right? > > > > Actually, it had been working perfectly with same configuration before i > > upgraded the server from sp3 to sp4. Did anything related to replication > > be > > changed in sp4? > > > > "Hilary Cotter" wrote: > > > >> You have two options. You can run the distribution agent continually to > >> minimize the impact occurring at 1:00 pm, or you can schedule it to stop > >> around 12:50 pm and restart when the other processes are complete. > >> > >> -- > >> 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 > >> > >> > >> > >> "ericsson" <ericsson@discussions.microsoft.com> wrote in message > >> news:827E13A7-26C0-4C0F-BC2B-D9DC48E34819@microsoft.com... > >> > hi all, > >> > > >> > my sql server has sp4 installed. i have two databases, D1 and D2. And > >> > the > >> > transaction replication copys table D1.T1 to D2.T1 at 1:00pm everyday. > >> > > >> > the problem is: > >> > when some applications are continuously using table D2.T1, i mean those > >> > processes are in runnable status. And then the replication starts and > >> > try > >> > to > >> > copy data from D1.T1 to D2.T1, it will fail. > >> > > >> > is there a way to work around this without having to kill those running > >> > process which are using table D2.T1 at that time? > >> > >> > >> > >
There were bug fixes, but none which has caused (AFAIK) this problem on
other systems. Perhaps you have another process running on your system at 1:00 am which is causing extra load on your system and the overall degradation is causing this problem to occur. -- 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] "ericsson" <ericsson@discussions.microsoft.com> wrote in message news:875E8A04-90D5-44E2-A13B-111C2E8CC143@microsoft.com... > Hi Hilary, > > Thank you for your information. i understand your words as: deliver > transactions only when no other processes are using table D2.T1, or using > continually transaction delivery, right? > > Actually, it had been working perfectly with same configuration before i > upgraded the server from sp3 to sp4. Did anything related to replication > be > changed in sp4? > > "Hilary Cotter" wrote: > >> You have two options. You can run the distribution agent continually to >> minimize the impact occurring at 1:00 pm, or you can schedule it to stop >> around 12:50 pm and restart when the other processes are complete. >> >> -- >> 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 >> >> >> >> "ericsson" <ericsson@discussions.microsoft.com> wrote in message >> news:827E13A7-26C0-4C0F-BC2B-D9DC48E34819@microsoft.com... >> > hi all, >> > >> > my sql server has sp4 installed. i have two databases, D1 and D2. And >> > the >> > transaction replication copys table D1.T1 to D2.T1 at 1:00pm everyday. >> > >> > the problem is: >> > when some applications are continuously using table D2.T1, i mean those >> > processes are in runnable status. And then the replication starts and >> > try >> > to >> > copy data from D1.T1 to D2.T1, it will fail. >> > >> > is there a way to work around this without having to kill those running >> > process which are using table D2.T1 at that time? >> >> >>
It is usually inevitable that there will be some blocking issues in this
circumstance. You can mitigate these by using NOLOCK or upgrading to SQL Server 2005 and using the read committed snapshot isolation level. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com .
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 |