Don't know why this job failed since I deleted and rebuilt the subscriber and
publisher last week. Can someone help?
Error detail says: 'Executed as user: FOSTER\sqlservice. Could not find
stored procedure ''. [SQLSTATE 42000] (Error 2812) Associated statement is
not prepared [SQLSTATE HY007] (Error 0). The step failed.'
Appreciate your time.
Tsuey
Tsuey,
please take a look at this to see if it applies:
http://support.microsoft.com/kb/884854
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 the quick reply. I read this article and don't think it apply.
I don't think I created the replication as transactional replication with
queued updating. If I did, SQL Server will add a new column in each
replicated table, right? How can I sure that the replication is not
configured as queued update?
Tsuey
"Paul Ibison" wrote:
> Tsuey,
> please take a look at this to see if it applies:
> http://support.microsoft.com/kb/884854
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Tsuey,
what is the 'update mode' if you run sp_helpsubscription?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul, I tried to execute sp_helpsubscription in Query analyzer (hope this
is the right tool to run it) but how do I display the result set? I set the
result in grid or text or file, but can not get the result set to display.
It just simply tells me 'The command(s) completed successfully'. What did I
do wrong? The syntax I use is as below:
exec sp_helpsubscription
GO
"Paul Ibison" wrote:
> Tsuey,
> what is the 'update mode' if you run sp_helpsubscription?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||You'll need to execute this at the publisher on the publication database and
provide the subscriber name.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul, I got the sp_helpsubscription ran successfully!! The update mode
for all rows are 0's. It means 'read-only'. What does this tell me? FYI,
we configure the replication as a push replication.
Thanks for your time,
Tsuey
"Paul Ibison" wrote:
> You'll need to execute this at the publisher on the publication database and
> provide the subscriber name.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||OK - then the article definitely doesn't apply. I'd be tempted to reapply
your latest service pack on the distributor, publisher then subscriber. If
that doesn't resolve this issue they I'd raise a support case.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul,
Thanks very much for your reply. I'll try appying the SP4 to see if it helps.
Tsuey
"Paul Ibison" wrote:
> OK - then the article definitely doesn't apply. I'd be tempted to reapply
> your latest service pack on the distributor, publisher then subscriber. If
> that doesn't resolve this issue they I'd raise a support case.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
Showing posts with label subscriber. Show all posts
Showing posts with label subscriber. Show all posts
Friday, March 30, 2012
Replication Error after Upgrade (7.0-2000)
Scenario: 3 servers - one Subscriber, one Distributor, one Publisher. Transactional replication; immediate updating subscribers disallowed. Each article in its own publication... independent agents.
Subscriber & Publisher = SQL 7.0
Distributor recently upgraded to 2000, SP3a.
Issue: new publications created at publisher fail to initialize snapshot agent properly. Error: "Another snapshot agent for the publication is running". Agent then fails after total retries (default is 10... does not matter what I set it to).
All existing publications work fine; all existing subscriptions work fine.
So what's the deal?
It appears that once you upgrade the Distributor(s), you have to upgrade the Publisher(s) immediately thereafter if you wish to create new publications. I have not seen that documented however... anyone know?
Thanks!
X
This is documented somewhat. Check out
http://msdn.microsoft.com/library/de...grade_45ir.asp
It doesn't say do this immediately though.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
news:D8EF5EEF-A0D7-4F69-B519-FD970A02F509@.microsoft.com...
> Scenario: 3 servers - one Subscriber, one Distributor, one Publisher.
Transactional replication; immediate updating subscribers disallowed. Each
article in its own publication... independent agents.
> Subscriber & Publisher = SQL 7.0
> Distributor recently upgraded to 2000, SP3a.
> Issue: new publications created at publisher fail to initialize snapshot
agent properly. Error: "Another snapshot agent for the publication is
running". Agent then fails after total retries (default is 10... does not
matter what I set it to).
> All existing publications work fine; all existing subscriptions work fine.
> So what's the deal?
> It appears that once you upgrade the Distributor(s), you have to upgrade
the Publisher(s) immediately thereafter if you wish to create new
publications. I have not seen that documented however... anyone know?
> Thanks!
> X
|||Thanks for the response Hilary.
I read that article; it doesn't specify that publishers MUST be upgraded to 2000 once the Distributor has been upgraded. That's the issue here: we have an upgraded Distributor, but we cannot upgrade the Publisher for some time. In the meantime, we need to
create new publications. We are unable to do so however, due to the error I outlined. It APPEARS that once you upgrade your Distributor, you have to upgrade your Publisher before you can create new publications. That doesn't seem right, but I have yet to
find evidence of its validity.
FWIW: one of the DBAs here reported the same error after applying SPs/hotfixes on the Distributor w/o applying same to Publisher.
"Hilary Cotter" wrote:
> This is documented somewhat. Check out
> http://msdn.microsoft.com/library/de...grade_45ir.asp
> It doesn't say do this immediately though.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
> news:D8EF5EEF-A0D7-4F69-B519-FD970A02F509@.microsoft.com...
> Transactional replication; immediate updating subscribers disallowed. Each
> article in its own publication... independent agents.
> agent properly. Error: "Another snapshot agent for the publication is
> running". Agent then fails after total retries (default is 10... does not
> matter what I set it to).
> the Publisher(s) immediately thereafter if you wish to create new
> publications. I have not seen that documented however... anyone know?
>
>
|||FYI: the following URL shows the configuration I outlined as a 'valid replication topology' http://msdn.microsoft.com/library/de...limpl_4joy.asp
However, it doe not indicate that new publications created on the 7.0 Publisher w/ 2k Distributor and 7.0 Subscriber(s) will fail. On the contrary - it leads one to believe that the new publications will be in 70 compatability mode, as the replication top
ology defaults to the lowest level in a mixed environment.
Odd then, that I get this error. (btw, we have recycled the servers)
"Hilary Cotter" wrote:
> This is documented somewhat. Check out
> http://msdn.microsoft.com/library/de...grade_45ir.asp
> It doesn't say do this immediately though.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
> news:D8EF5EEF-A0D7-4F69-B519-FD970A02F509@.microsoft.com...
> Transactional replication; immediate updating subscribers disallowed. Each
> article in its own publication... independent agents.
> agent properly. Error: "Another snapshot agent for the publication is
> running". Agent then fails after total retries (default is 10... does not
> matter what I set it to).
> the Publisher(s) immediately thereafter if you wish to create new
> publications. I have not seen that documented however... anyone know?
>
>
|||Let me try to repro this tonight.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
news:9034767C-3D75-4C7B-B975-510CC8AFDFDD@.microsoft.com...
> Thanks for the response Hilary.
> I read that article; it doesn't specify that publishers MUST be upgraded
to 2000 once the Distributor has been upgraded. That's the issue here: we
have an upgraded Distributor, but we cannot upgrade the Publisher for some
time. In the meantime, we need to create new publications. We are unable to
do so however, due to the error I outlined. It APPEARS that once you upgrade
your Distributor, you have to upgrade your Publisher before you can create
new publications. That doesn't seem right, but I have yet to find evidence
of its validity.
> FWIW: one of the DBAs here reported the same error after applying
SPs/hotfixes on the Distributor w/o applying same to Publisher.[vbcol=seagreen]
> "Hilary Cotter" wrote:
http://msdn.microsoft.com/library/de...grade_45ir.asp[vbcol=seagreen]
Each[vbcol=seagreen]
snapshot[vbcol=seagreen]
not[vbcol=seagreen]
fine.[vbcol=seagreen]
upgrade[vbcol=seagreen]
|||Were you able to reproduce the error?
Many thanks!!
X
"Hilary Cotter" wrote:
> Let me try to repro this tonight.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
> news:9034767C-3D75-4C7B-B975-510CC8AFDFDD@.microsoft.com...
> to 2000 once the Distributor has been upgraded. That's the issue here: we
> have an upgraded Distributor, but we cannot upgrade the Publisher for some
> time. In the meantime, we need to create new publications. We are unable to
> do so however, due to the error I outlined. It APPEARS that once you upgrade
> your Distributor, you have to upgrade your Publisher before you can create
> new publications. That doesn't seem right, but I have yet to find evidence
> of its validity.
> SPs/hotfixes on the Distributor w/o applying same to Publisher.
> http://msdn.microsoft.com/library/de...grade_45ir.asp
> Each
> snapshot
> not
> fine.
> upgrade
>
>
|||No, I was unable to get the error. What error did you get, and what service
packs were you running?
Where you using an Administrative Link password?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
news:C359EA3E-0ED4-417C-B1A9-F4F015253BD0@.microsoft.com...[vbcol=seagreen]
> Were you able to reproduce the error?
> Many thanks!!
> X
>
> "Hilary Cotter" wrote:
upgraded[vbcol=seagreen]
we[vbcol=seagreen]
some[vbcol=seagreen]
to[vbcol=seagreen]
upgrade[vbcol=seagreen]
create[vbcol=seagreen]
evidence[vbcol=seagreen]
http://msdn.microsoft.com/library/de...grade_45ir.asp[vbcol=seagreen]
Publisher.[vbcol=seagreen]
disallowed.[vbcol=seagreen]
is[vbcol=seagreen]
does[vbcol=seagreen]
work[vbcol=seagreen]
know?[vbcol=seagreen]
sql
Subscriber & Publisher = SQL 7.0
Distributor recently upgraded to 2000, SP3a.
Issue: new publications created at publisher fail to initialize snapshot agent properly. Error: "Another snapshot agent for the publication is running". Agent then fails after total retries (default is 10... does not matter what I set it to).
All existing publications work fine; all existing subscriptions work fine.
So what's the deal?
It appears that once you upgrade the Distributor(s), you have to upgrade the Publisher(s) immediately thereafter if you wish to create new publications. I have not seen that documented however... anyone know?
Thanks!
X
This is documented somewhat. Check out
http://msdn.microsoft.com/library/de...grade_45ir.asp
It doesn't say do this immediately though.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
news:D8EF5EEF-A0D7-4F69-B519-FD970A02F509@.microsoft.com...
> Scenario: 3 servers - one Subscriber, one Distributor, one Publisher.
Transactional replication; immediate updating subscribers disallowed. Each
article in its own publication... independent agents.
> Subscriber & Publisher = SQL 7.0
> Distributor recently upgraded to 2000, SP3a.
> Issue: new publications created at publisher fail to initialize snapshot
agent properly. Error: "Another snapshot agent for the publication is
running". Agent then fails after total retries (default is 10... does not
matter what I set it to).
> All existing publications work fine; all existing subscriptions work fine.
> So what's the deal?
> It appears that once you upgrade the Distributor(s), you have to upgrade
the Publisher(s) immediately thereafter if you wish to create new
publications. I have not seen that documented however... anyone know?
> Thanks!
> X
|||Thanks for the response Hilary.
I read that article; it doesn't specify that publishers MUST be upgraded to 2000 once the Distributor has been upgraded. That's the issue here: we have an upgraded Distributor, but we cannot upgrade the Publisher for some time. In the meantime, we need to
create new publications. We are unable to do so however, due to the error I outlined. It APPEARS that once you upgrade your Distributor, you have to upgrade your Publisher before you can create new publications. That doesn't seem right, but I have yet to
find evidence of its validity.
FWIW: one of the DBAs here reported the same error after applying SPs/hotfixes on the Distributor w/o applying same to Publisher.
"Hilary Cotter" wrote:
> This is documented somewhat. Check out
> http://msdn.microsoft.com/library/de...grade_45ir.asp
> It doesn't say do this immediately though.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
> news:D8EF5EEF-A0D7-4F69-B519-FD970A02F509@.microsoft.com...
> Transactional replication; immediate updating subscribers disallowed. Each
> article in its own publication... independent agents.
> agent properly. Error: "Another snapshot agent for the publication is
> running". Agent then fails after total retries (default is 10... does not
> matter what I set it to).
> the Publisher(s) immediately thereafter if you wish to create new
> publications. I have not seen that documented however... anyone know?
>
>
|||FYI: the following URL shows the configuration I outlined as a 'valid replication topology' http://msdn.microsoft.com/library/de...limpl_4joy.asp
However, it doe not indicate that new publications created on the 7.0 Publisher w/ 2k Distributor and 7.0 Subscriber(s) will fail. On the contrary - it leads one to believe that the new publications will be in 70 compatability mode, as the replication top
ology defaults to the lowest level in a mixed environment.
Odd then, that I get this error. (btw, we have recycled the servers)
"Hilary Cotter" wrote:
> This is documented somewhat. Check out
> http://msdn.microsoft.com/library/de...grade_45ir.asp
> It doesn't say do this immediately though.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
> news:D8EF5EEF-A0D7-4F69-B519-FD970A02F509@.microsoft.com...
> Transactional replication; immediate updating subscribers disallowed. Each
> article in its own publication... independent agents.
> agent properly. Error: "Another snapshot agent for the publication is
> running". Agent then fails after total retries (default is 10... does not
> matter what I set it to).
> the Publisher(s) immediately thereafter if you wish to create new
> publications. I have not seen that documented however... anyone know?
>
>
|||Let me try to repro this tonight.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
news:9034767C-3D75-4C7B-B975-510CC8AFDFDD@.microsoft.com...
> Thanks for the response Hilary.
> I read that article; it doesn't specify that publishers MUST be upgraded
to 2000 once the Distributor has been upgraded. That's the issue here: we
have an upgraded Distributor, but we cannot upgrade the Publisher for some
time. In the meantime, we need to create new publications. We are unable to
do so however, due to the error I outlined. It APPEARS that once you upgrade
your Distributor, you have to upgrade your Publisher before you can create
new publications. That doesn't seem right, but I have yet to find evidence
of its validity.
> FWIW: one of the DBAs here reported the same error after applying
SPs/hotfixes on the Distributor w/o applying same to Publisher.[vbcol=seagreen]
> "Hilary Cotter" wrote:
http://msdn.microsoft.com/library/de...grade_45ir.asp[vbcol=seagreen]
Each[vbcol=seagreen]
snapshot[vbcol=seagreen]
not[vbcol=seagreen]
fine.[vbcol=seagreen]
upgrade[vbcol=seagreen]
|||Were you able to reproduce the error?
Many thanks!!
X
"Hilary Cotter" wrote:
> Let me try to repro this tonight.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
> news:9034767C-3D75-4C7B-B975-510CC8AFDFDD@.microsoft.com...
> to 2000 once the Distributor has been upgraded. That's the issue here: we
> have an upgraded Distributor, but we cannot upgrade the Publisher for some
> time. In the meantime, we need to create new publications. We are unable to
> do so however, due to the error I outlined. It APPEARS that once you upgrade
> your Distributor, you have to upgrade your Publisher before you can create
> new publications. That doesn't seem right, but I have yet to find evidence
> of its validity.
> SPs/hotfixes on the Distributor w/o applying same to Publisher.
> http://msdn.microsoft.com/library/de...grade_45ir.asp
> Each
> snapshot
> not
> fine.
> upgrade
>
>
|||No, I was unable to get the error. What error did you get, and what service
packs were you running?
Where you using an Administrative Link password?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Xfonhe" <Xfonhe@.discussions.microsoft.com> wrote in message
news:C359EA3E-0ED4-417C-B1A9-F4F015253BD0@.microsoft.com...[vbcol=seagreen]
> Were you able to reproduce the error?
> Many thanks!!
> X
>
> "Hilary Cotter" wrote:
upgraded[vbcol=seagreen]
we[vbcol=seagreen]
some[vbcol=seagreen]
to[vbcol=seagreen]
upgrade[vbcol=seagreen]
create[vbcol=seagreen]
evidence[vbcol=seagreen]
http://msdn.microsoft.com/library/de...grade_45ir.asp[vbcol=seagreen]
Publisher.[vbcol=seagreen]
disallowed.[vbcol=seagreen]
is[vbcol=seagreen]
does[vbcol=seagreen]
work[vbcol=seagreen]
know?[vbcol=seagreen]
sql
Wednesday, March 28, 2012
Replication error (old Snapshotfiles)
Basically your snapshot does not contain enough information in it to deploy
a new subscriber and then backfill it with changes which have occurred on
the publisher so the subscriber can merge with the publisher.
To do this you need a new snapshot. You might need to change your retention
period to something larger.
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
"Jonas Jegler" <jonas.jegler@.siegel-edv.de> wrote in message
news:OSTIybWNHHA.3944@.TK2MSFTNGP06.phx.gbl...
> We have a SQL Server 2005 Merge Replication to an SQL Server 2005 EXPRESS
> EDITION.
> After indefinable time intervals the error message:
> "They must again implement the Snapshot, since the current Snapshotfiles
> became outdated"
> comes.
> Can someone say something to me about the error message?
>
how frequently is your snapshot generated?
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
"Jonas Jegler" <jonas.jegler@.siegel-edv.de> wrote in message
news:Oc$SQejNHHA.4912@.TK2MSFTNGP02.phx.gbl...
> thankyou for your answer.
> we can do the Replication in each direction. but after indefinable time we
> becomes the error message:
> "They must again implement the Snapshot, since the current Snapshotfiles
> became outdated"
> where can i change the retention period?
>
a new subscriber and then backfill it with changes which have occurred on
the publisher so the subscriber can merge with the publisher.
To do this you need a new snapshot. You might need to change your retention
period to something larger.
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
"Jonas Jegler" <jonas.jegler@.siegel-edv.de> wrote in message
news:OSTIybWNHHA.3944@.TK2MSFTNGP06.phx.gbl...
> We have a SQL Server 2005 Merge Replication to an SQL Server 2005 EXPRESS
> EDITION.
> After indefinable time intervals the error message:
> "They must again implement the Snapshot, since the current Snapshotfiles
> became outdated"
> comes.
> Can someone say something to me about the error message?
>
how frequently is your snapshot generated?
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
"Jonas Jegler" <jonas.jegler@.siegel-edv.de> wrote in message
news:Oc$SQejNHHA.4912@.TK2MSFTNGP02.phx.gbl...
> thankyou for your answer.
> we can do the Replication in each direction. but after indefinable time we
> becomes the error message:
> "They must again implement the Snapshot, since the current Snapshotfiles
> became outdated"
> where can i change the retention period?
>
replication error
Hi,
I have configured transactional replication with one publisher and one subscriber.
after completion of schema and bcp operation , it has given message as "posting commands into the distribution database" after that timedout expired .
Now the error message is
"The concurrent snapshot for publication 'Siebel OLTP Transactional' has not been activated by the log reader agent" and schema in shared folder got deleted and snopshat agent started again.
Pls provide resolution
Thanks
Murali
Murali,
you could try increasing the -QUERYTIMEOUT parameter of the distribution
agent's profile. The second error might be resulting from the first, but
just in case it isn't I'd increase the -QUERYTIMEOUT of the logreader also.
I'm not too sure where your post title fits in - "Space is not available in
TempDB" - did you also see this error message? Obviously in this case TempDB
needs increasing in size.
HTH,
Paul Ibison
|||I'd try setting the QueryTimeout parameter in the Snapshot agent.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23tDHzD3YEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Murali,
> you could try increasing the -QUERYTIMEOUT parameter of the distribution
> agent's profile. The second error might be resulting from the first, but
> just in case it isn't I'd increase the -QUERYTIMEOUT of the logreader
also.
> I'm not too sure where your post title fits in - "Space is not available
in
> TempDB" - did you also see this error message? Obviously in this case
TempDB
> needs increasing in size.
> HTH,
> Paul Ibison
>
I have configured transactional replication with one publisher and one subscriber.
after completion of schema and bcp operation , it has given message as "posting commands into the distribution database" after that timedout expired .
Now the error message is
"The concurrent snapshot for publication 'Siebel OLTP Transactional' has not been activated by the log reader agent" and schema in shared folder got deleted and snopshat agent started again.
Pls provide resolution
Thanks
Murali
Murali,
you could try increasing the -QUERYTIMEOUT parameter of the distribution
agent's profile. The second error might be resulting from the first, but
just in case it isn't I'd increase the -QUERYTIMEOUT of the logreader also.
I'm not too sure where your post title fits in - "Space is not available in
TempDB" - did you also see this error message? Obviously in this case TempDB
needs increasing in size.
HTH,
Paul Ibison
|||I'd try setting the QueryTimeout parameter in the Snapshot agent.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23tDHzD3YEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Murali,
> you could try increasing the -QUERYTIMEOUT parameter of the distribution
> agent's profile. The second error might be resulting from the first, but
> just in case it isn't I'd increase the -QUERYTIMEOUT of the logreader
also.
> I'm not too sure where your post title fits in - "Space is not available
in
> TempDB" - did you also see this error message? Obviously in this case
TempDB
> needs increasing in size.
> HTH,
> Paul Ibison
>
Replication Error
Hi ,
I have set up some push replication i.e i subscriber and multipler publisher
and i found that in one country the replication failed
it says "subscription is marked inactive and must be re-initialized"
how do i check the error ? and how i can resolved this error ?
tks & rdgsHi
http://groups.google.ch/groups?hl=en&lr=&threadm=108401c36123%24814cf5c0%24a001280a%40phx.gbl&rnum=1&prev=/groups%3Fq%3Dsubscription%2Bmarked%2Binactive%26hl%3Den%26lr%3D%26selm%3D108401c36123%2524814cf5c0%2524a001280a%2540phx.gbl%26rnum%3D1
Regards
Mike
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publisher
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs|||Hi Mike,
the link that you provided is really useful
tks & rdgs
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> http://groups.google.ch/groups?hl=en&lr=&threadm=108401c36123%24814cf5c0%24a001280a%40phx.gbl&rnum=1&prev=/groups%3Fq%3Dsubscription%2Bmarked%2Binactive%26hl%3Den%26lr%3D%26selm%3D108401c36123%2524814cf5c0%2524a001280a%2540phx.gbl%26rnum%3D1
> Regards
> Mike
> "maxzsim" wrote:
> > Hi ,
> >
> > I have set up some push replication i.e i subscriber and multipler publisher
> > and i found that in one country the replication failed
> > it says "subscription is marked inactive and must be re-initialized"
> >
> > how do i check the error ? and how i can resolved this error ?
> >
> > tks & rdgs|||Hi after looking at this issue I would refer to this article to determine how
to resolve this issue.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replmon_92ge.asp
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publisher
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs
I have set up some push replication i.e i subscriber and multipler publisher
and i found that in one country the replication failed
it says "subscription is marked inactive and must be re-initialized"
how do i check the error ? and how i can resolved this error ?
tks & rdgsHi
http://groups.google.ch/groups?hl=en&lr=&threadm=108401c36123%24814cf5c0%24a001280a%40phx.gbl&rnum=1&prev=/groups%3Fq%3Dsubscription%2Bmarked%2Binactive%26hl%3Den%26lr%3D%26selm%3D108401c36123%2524814cf5c0%2524a001280a%2540phx.gbl%26rnum%3D1
Regards
Mike
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publisher
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs|||Hi Mike,
the link that you provided is really useful
tks & rdgs
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> http://groups.google.ch/groups?hl=en&lr=&threadm=108401c36123%24814cf5c0%24a001280a%40phx.gbl&rnum=1&prev=/groups%3Fq%3Dsubscription%2Bmarked%2Binactive%26hl%3Den%26lr%3D%26selm%3D108401c36123%2524814cf5c0%2524a001280a%2540phx.gbl%26rnum%3D1
> Regards
> Mike
> "maxzsim" wrote:
> > Hi ,
> >
> > I have set up some push replication i.e i subscriber and multipler publisher
> > and i found that in one country the replication failed
> > it says "subscription is marked inactive and must be re-initialized"
> >
> > how do i check the error ? and how i can resolved this error ?
> >
> > tks & rdgs|||Hi after looking at this issue I would refer to this article to determine how
to resolve this issue.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replmon_92ge.asp
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publisher
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs
Replication Error
I am using Replication wizard and created Publisher with
name "Services3 and Subscriber is HOffice with
Subscription database is GinFactory1 and using Windows
authentication Mode. Subscription is Push Subscription.
It create sanapshot and also transfer data in GinFactory1
as soon as Wizard has been completed. But when i try to
synchronize Subscription using option start sunchronizing
it returns error "Publication is invalid" .What can be
reason of it?Please give me detail description if u have.
Thanks in advance
Normally the publication is invalid error message means that your snapshot
files are too old. Can you regenerate your snapshot (right click on your
snapshot agent and select start agent), and then restart your distribution
agent?
You may get a message telling you the no snapshot was generated as
subscriptions needed reinitialization.
If you get this message right click on your publication, publication
properties, go to the subscribers tab, located your subscriber and click
reinitialize. Then restart your snapshot agent.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Saima" <ucoxk@.yahoo.com> wrote in message
news:3fa701c47308$49893d40$a601280a@.phx.gbl...
> I am using Replication wizard and created Publisher with
> name "Services3 and Subscriber is HOffice with
> Subscription database is GinFactory1 and using Windows
> authentication Mode. Subscription is Push Subscription.
> It create sanapshot and also transfer data in GinFactory1
> as soon as Wizard has been completed. But when i try to
> synchronize Subscription using option start sunchronizing
> it returns error "Publication is invalid" .What can be
> reason of it?Please give me detail description if u have.
> Thanks in advance
|||It is not too old . i just do it after 5 minutes
>--Original Message--
>Normally the publication is invalid error message means
that your snapshot
>files are too old. Can you regenerate your snapshot
(right click on your
>snapshot agent and select start agent), and then restart
your distribution
>agent?
>You may get a message telling you the no snapshot was
generated as
>subscriptions needed reinitialization.
>If you get this message right click on your publication,
publication
>properties, go to the subscribers tab, located your
subscriber and click[vbcol=seagreen]
>reinitialize. Then restart your snapshot agent.
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"Saima" <ucoxk@.yahoo.com> wrote in message
>news:3fa701c47308$49893d40$a601280a@.phx.gbl...
with[vbcol=seagreen]
GinFactory1[vbcol=seagreen]
sunchronizing[vbcol=seagreen]
have.
>
>.
>
|||can you script out your publication and post it here?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Saima" <ucoxk@.yahoo.com> wrote in message
news:44de01c4733d$c1287570$a601280a@.phx.gbl...[vbcol=seagreen]
> It is not too old . i just do it after 5 minutes
> that your snapshot
> (right click on your
> your distribution
> generated as
> publication
> subscriber and click
> with
> GinFactory1
> sunchronizing
> have.
name "Services3 and Subscriber is HOffice with
Subscription database is GinFactory1 and using Windows
authentication Mode. Subscription is Push Subscription.
It create sanapshot and also transfer data in GinFactory1
as soon as Wizard has been completed. But when i try to
synchronize Subscription using option start sunchronizing
it returns error "Publication is invalid" .What can be
reason of it?Please give me detail description if u have.
Thanks in advance
Normally the publication is invalid error message means that your snapshot
files are too old. Can you regenerate your snapshot (right click on your
snapshot agent and select start agent), and then restart your distribution
agent?
You may get a message telling you the no snapshot was generated as
subscriptions needed reinitialization.
If you get this message right click on your publication, publication
properties, go to the subscribers tab, located your subscriber and click
reinitialize. Then restart your snapshot agent.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Saima" <ucoxk@.yahoo.com> wrote in message
news:3fa701c47308$49893d40$a601280a@.phx.gbl...
> I am using Replication wizard and created Publisher with
> name "Services3 and Subscriber is HOffice with
> Subscription database is GinFactory1 and using Windows
> authentication Mode. Subscription is Push Subscription.
> It create sanapshot and also transfer data in GinFactory1
> as soon as Wizard has been completed. But when i try to
> synchronize Subscription using option start sunchronizing
> it returns error "Publication is invalid" .What can be
> reason of it?Please give me detail description if u have.
> Thanks in advance
|||It is not too old . i just do it after 5 minutes
>--Original Message--
>Normally the publication is invalid error message means
that your snapshot
>files are too old. Can you regenerate your snapshot
(right click on your
>snapshot agent and select start agent), and then restart
your distribution
>agent?
>You may get a message telling you the no snapshot was
generated as
>subscriptions needed reinitialization.
>If you get this message right click on your publication,
publication
>properties, go to the subscribers tab, located your
subscriber and click[vbcol=seagreen]
>reinitialize. Then restart your snapshot agent.
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"Saima" <ucoxk@.yahoo.com> wrote in message
>news:3fa701c47308$49893d40$a601280a@.phx.gbl...
with[vbcol=seagreen]
GinFactory1[vbcol=seagreen]
sunchronizing[vbcol=seagreen]
have.
>
>.
>
|||can you script out your publication and post it here?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Saima" <ucoxk@.yahoo.com> wrote in message
news:44de01c4733d$c1287570$a601280a@.phx.gbl...[vbcol=seagreen]
> It is not too old . i just do it after 5 minutes
> that your snapshot
> (right click on your
> your distribution
> generated as
> publication
> subscriber and click
> with
> GinFactory1
> sunchronizing
> have.
Replication Error
Hi ,
I have set up some push replication i.e i subscriber and multipler publisher
and i found that in one country the replication failed
it says "subscription is marked inactive and must be re-initialized"
how do i check the error ? and how i can resolved this error ?
tks & rdgs
Hi
http://groups.google.ch/groups?hl=en...gbl%26rnum%3D1
Regards
Mike
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publisher
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs
|||Hi Mike,
the link that you provided is really useful
tks & rdgs
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> http://groups.google.ch/groups?hl=en...gbl%26rnum%3D1
> Regards
> Mike
> "maxzsim" wrote:
|||Hi after looking at this issue I would refer to this article to determine how
to resolve this issue.
http://msdn.microsoft.com/library/de...plmon_92ge.asp
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publisher
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs
I have set up some push replication i.e i subscriber and multipler publisher
and i found that in one country the replication failed
it says "subscription is marked inactive and must be re-initialized"
how do i check the error ? and how i can resolved this error ?
tks & rdgs
Hi
http://groups.google.ch/groups?hl=en...gbl%26rnum%3D1
Regards
Mike
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publisher
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs
|||Hi Mike,
the link that you provided is really useful
tks & rdgs
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> http://groups.google.ch/groups?hl=en...gbl%26rnum%3D1
> Regards
> Mike
> "maxzsim" wrote:
|||Hi after looking at this issue I would refer to this article to determine how
to resolve this issue.
http://msdn.microsoft.com/library/de...plmon_92ge.asp
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publisher
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs
Replication Error
Hi ,
I have set up some push replication i.e i subscriber and multipler publisher
and i found that in one country the replication failed
it says "subscription is marked inactive and must be re-initialized"
how do i check the error ? and how i can resolved this error ?
tks & rdgsHi
[url]http://groups.google.ch/groups?hl=en&lr=& threadm=108401c36123%24814cf5c0%24a00128
0
a%40phx.gbl&rnum=1&prev=/ groups%3Fq%3Dsubscription%2Bmarked%2Bina
ctive%26hl%3Den%2
6lr%3D%26selm%3D108401c36123%2524814cf5c
0%2524a001280a%2540phx.gbl%26rnum%3D1[/url
]
Regards
Mike
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publis
her
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs|||Hi Mike,
the link that you provided is really useful
tks & rdgs
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> [url]http://groups.google.ch/groups?hl=en&lr=&threadm=108401c36123%24814cf5c0%24a0012
80a%40phx.gbl&rnum=1&prev=/ groups%3Fq%3Dsubscription%2Bmarked%2Bina
ctive%26hl%3Den
%26lr%3D%26selm%3D108401c36123%2524814cf
5c0%2524a001280a%2540phx.gbl%26rnum%3D1[/u
rl]
> Regards
> Mike
> "maxzsim" wrote:
>|||Hi after looking at this issue I would refer to this article to determine ho
w
to resolve this issue.
2ge.asp" target="_blank">http://msdn.microsoft.com/library/d...
2ge.asp
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publis
her
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs
I have set up some push replication i.e i subscriber and multipler publisher
and i found that in one country the replication failed
it says "subscription is marked inactive and must be re-initialized"
how do i check the error ? and how i can resolved this error ?
tks & rdgsHi
[url]http://groups.google.ch/groups?hl=en&lr=& threadm=108401c36123%24814cf5c0%24a00128
0
a%40phx.gbl&rnum=1&prev=/ groups%3Fq%3Dsubscription%2Bmarked%2Bina
ctive%26hl%3Den%2
6lr%3D%26selm%3D108401c36123%2524814cf5c
0%2524a001280a%2540phx.gbl%26rnum%3D1[/url
]
Regards
Mike
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publis
her
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs|||Hi Mike,
the link that you provided is really useful
tks & rdgs
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> [url]http://groups.google.ch/groups?hl=en&lr=&threadm=108401c36123%24814cf5c0%24a0012
80a%40phx.gbl&rnum=1&prev=/ groups%3Fq%3Dsubscription%2Bmarked%2Bina
ctive%26hl%3Den
%26lr%3D%26selm%3D108401c36123%2524814cf
5c0%2524a001280a%2540phx.gbl%26rnum%3D1[/u
rl]
> Regards
> Mike
> "maxzsim" wrote:
>|||Hi after looking at this issue I would refer to this article to determine ho
w
to resolve this issue.
2ge.asp" target="_blank">http://msdn.microsoft.com/library/d...
2ge.asp
"maxzsim" wrote:
> Hi ,
> I have set up some push replication i.e i subscriber and multipler publis
her
> and i found that in one country the replication failed
> it says "subscription is marked inactive and must be re-initialized"
> how do i check the error ? and how i can resolved this error ?
> tks & rdgs
Monday, March 26, 2012
Replication does not work properly
Hi,
I have a problem with rows deleted at subscriber could not get deleted at
publisher in particular case where article published say table1 has row
filter like
"SELECT <published_columns> FROM [dbo].[TABLE1]
WHERE ([FILED1]='XYZ ' OR [FIELD4]= 'XYZ ') and FIELD3 in(select
[FIELD3] from [TABLE2] A where A.[FIELD1]=[FIELD1] and A.[FIELD2]=[FIELD2] )"
Rest of the Articles published with simpler row filter works perfectly.
Please Reply,
Thanking You
fatiya
are both Table1 and Table2 published? are there any constraints between teh
two tables? Are you enforcing these constraints for replication? Cascading
Updates/Deletes?
Have you used the conflict viewer to see if there are any conflicts?
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
"Fatiya" <Fatiya@.discussions.microsoft.com> wrote in message
news:6A20CE4B-7D05-4202-BCEE-79AC26E28326@.microsoft.com...
> Hi,
> I have a problem with rows deleted at subscriber could not get deleted
at
> publisher in particular case where article published say table1 has row
> filter like
> "SELECT <published_columns> FROM [dbo].[TABLE1]
> WHERE ([FILED1]='XYZ ' OR [FIELD4]= 'XYZ ') and FIELD3 in(select
> [FIELD3] from [TABLE2] A where A.[FIELD1]=[FIELD1] and
A.[FIELD2]=[FIELD2] )"
> Rest of the Articles published with simpler row filter works perfectly.
> Please Reply,
> Thanking You
> fatiya
>
>
|||Dear Hilary
Thanks for reply
Yes both table 1 and table2 are published No there are no contrainst between
them
we have not used any cascading
We are getting replicaion conflicts that the row was inserted at subscriber
but
at publisher we are getting primary key constrains.
Please advice
Fatiya
"Hilary Cotter" wrote:
> are both Table1 and Table2 published? are there any constraints between teh
> two tables? Are you enforcing these constraints for replication? Cascading
> Updates/Deletes?
> Have you used the conflict viewer to see if there are any conflicts?
> --
> 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
> "Fatiya" <Fatiya@.discussions.microsoft.com> wrote in message
> news:6A20CE4B-7D05-4202-BCEE-79AC26E28326@.microsoft.com...
> at
> A.[FIELD2]=[FIELD2] )"
>
>
sql
I have a problem with rows deleted at subscriber could not get deleted at
publisher in particular case where article published say table1 has row
filter like
"SELECT <published_columns> FROM [dbo].[TABLE1]
WHERE ([FILED1]='XYZ ' OR [FIELD4]= 'XYZ ') and FIELD3 in(select
[FIELD3] from [TABLE2] A where A.[FIELD1]=[FIELD1] and A.[FIELD2]=[FIELD2] )"
Rest of the Articles published with simpler row filter works perfectly.
Please Reply,
Thanking You
fatiya
are both Table1 and Table2 published? are there any constraints between teh
two tables? Are you enforcing these constraints for replication? Cascading
Updates/Deletes?
Have you used the conflict viewer to see if there are any conflicts?
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
"Fatiya" <Fatiya@.discussions.microsoft.com> wrote in message
news:6A20CE4B-7D05-4202-BCEE-79AC26E28326@.microsoft.com...
> Hi,
> I have a problem with rows deleted at subscriber could not get deleted
at
> publisher in particular case where article published say table1 has row
> filter like
> "SELECT <published_columns> FROM [dbo].[TABLE1]
> WHERE ([FILED1]='XYZ ' OR [FIELD4]= 'XYZ ') and FIELD3 in(select
> [FIELD3] from [TABLE2] A where A.[FIELD1]=[FIELD1] and
A.[FIELD2]=[FIELD2] )"
> Rest of the Articles published with simpler row filter works perfectly.
> Please Reply,
> Thanking You
> fatiya
>
>
|||Dear Hilary
Thanks for reply
Yes both table 1 and table2 are published No there are no contrainst between
them
we have not used any cascading
We are getting replicaion conflicts that the row was inserted at subscriber
but
at publisher we are getting primary key constrains.
Please advice
Fatiya
"Hilary Cotter" wrote:
> are both Table1 and Table2 published? are there any constraints between teh
> two tables? Are you enforcing these constraints for replication? Cascading
> Updates/Deletes?
> Have you used the conflict viewer to see if there are any conflicts?
> --
> 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
> "Fatiya" <Fatiya@.discussions.microsoft.com> wrote in message
> news:6A20CE4B-7D05-4202-BCEE-79AC26E28326@.microsoft.com...
> at
> A.[FIELD2]=[FIELD2] )"
>
>
sql
Replication Distributor Version
What is the minimum SQL Server version I can use on my replication distributor server? My publisher and subscriber(s) will all be Enterprise Edition (64 bit). However, it seems awefully wasteful to put Enterprise Edition on a box that is just used for distribution. That's another $15K for a server that doesn't do much. Can I use a lower version (Express, Developer, Standard)?
Thank you,
Ben Wolf
This page (http://msdn2.microsoft.com/en-us/library/ms143761.aspx) lists the features (including replication) that are supported by various editions of SQL server. (Go all the way to the bottom for replication)
Basically, Express is not supproted for distributor. Developer edition includes all the functionalities of Enterprise edition SQL server, but it is only licensed for development and/or test purpose, not as a production server.
Peng
|||Thank you, Peng. This is exactly what I needed. Looks like SE is the one for my distributor.
Thanks again,
Ben
sqlReplication Distributor Version
What is the minimum SQL Server version I can use on my replication distributor server? My publisher and subscriber(s) will all be Enterprise Edition (64 bit). However, it seems awefully wasteful to put Enterprise Edition on a box that is just used for distribution. That's another $15K for a server that doesn't do much. Can I use a lower version (Express, Developer, Standard)?
Thank you,
Ben Wolf
This page (http://msdn2.microsoft.com/en-us/library/ms143761.aspx) lists the features (including replication) that are supported by various editions of SQL server. (Go all the way to the bottom for replication)
Basically, Express is not supproted for distributor. Developer edition includes all the functionalities of Enterprise edition SQL server, but it is only licensed for development and/or test purpose, not as a production server.
Peng
|||Thank you, Peng. This is exactly what I needed. Looks like SE is the one for my distributor.
Thanks again,
Ben
Replication Distribution Agent cpu continues to grow
We have transactional replication set up. The agent is running on the
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cpu.
Is there a profile setting that I'm missing?
Thanks all in advance!!
Message posted via http://www.droptable.com
On Mar 1, 1:39 pm, "fnadal via droptable.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over a
> million cpu and continued to grow until I stopped and restarted the the pull
> subscription agent on the distribution server. Then it went down to about a
> hundred cpu. As I'm writing this article its already up to three thousand cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.droptable.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?
|||The cpu usage. When I do a select spid,loginame,program_name, cpu from master.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million for
that agent.
Tracy McKibben wrote:
>[quoted text clipped - 9 lines]
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
Message posted via http://www.droptable.com
|||That is a cumulative value since the connection started, not an immediate
usage value.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via droptable.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
> --
> Message posted via http://www.droptable.com
>
|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:[vbcol=seagreen]
>That is a cumulative value since the connection started, not an immediate
>usage value.
>[quoted text clipped - 12 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cpu.
Is there a profile setting that I'm missing?
Thanks all in advance!!
Message posted via http://www.droptable.com
On Mar 1, 1:39 pm, "fnadal via droptable.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over a
> million cpu and continued to grow until I stopped and restarted the the pull
> subscription agent on the distribution server. Then it went down to about a
> hundred cpu. As I'm writing this article its already up to three thousand cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.droptable.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?
|||The cpu usage. When I do a select spid,loginame,program_name, cpu from master.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million for
that agent.
Tracy McKibben wrote:
>[quoted text clipped - 9 lines]
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
Message posted via http://www.droptable.com
|||That is a cumulative value since the connection started, not an immediate
usage value.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via droptable.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
> --
> Message posted via http://www.droptable.com
>
|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:[vbcol=seagreen]
>That is a cumulative value since the connection started, not an immediate
>usage value.
>[quoted text clipped - 12 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1
Replication Distribution Agent cpu continues to grow
We have transactional replication set up. The agent is running on the
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cp
u.
Is there a profile setting that I'm missing?
Thanks all in advance!!
Message posted via http://www.droptable.comOn Mar 1, 1:39 pm, "fnadal via droptable.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over
a
> million cpu and continued to grow until I stopped and restarted the the pu
ll
> subscription agent on the distribution server. Then it went down to about
a
> hundred cpu. As I'm writing this article its already up to three thousand
cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.droptable.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?|||The cpu usage. When I do a select spid,loginame,program_name, cpu from maste
r.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million fo
r
that agent.
Tracy McKibben wrote:
>[quoted text clipped - 9 lines]
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
Message posted via http://www.droptable.com|||That is a cumulative value since the connection started, not an immediate
usage value.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via droptable.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
> --
> Message posted via http://www.droptable.com
>|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:[vbcol=seagreen]
>That is a cumulative value since the connection started, not an immediate
>usage value.
>
>[quoted text clipped - 12 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200703/1sql
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cp
u.
Is there a profile setting that I'm missing?
Thanks all in advance!!
Message posted via http://www.droptable.comOn Mar 1, 1:39 pm, "fnadal via droptable.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over
a
> million cpu and continued to grow until I stopped and restarted the the pu
ll
> subscription agent on the distribution server. Then it went down to about
a
> hundred cpu. As I'm writing this article its already up to three thousand
cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.droptable.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?|||The cpu usage. When I do a select spid,loginame,program_name, cpu from maste
r.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million fo
r
that agent.
Tracy McKibben wrote:
>[quoted text clipped - 9 lines]
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
Message posted via http://www.droptable.com|||That is a cumulative value since the connection started, not an immediate
usage value.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via droptable.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
> --
> Message posted via http://www.droptable.com
>|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:[vbcol=seagreen]
>That is a cumulative value since the connection started, not an immediate
>usage value.
>
>[quoted text clipped - 12 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200703/1sql
Replication Distribution Agent cpu continues to grow
We have transactional replication set up. The agent is running on the
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cpu.
Is there a profile setting that I'm missing?
Thanks all in advance!!
--
Message posted via http://www.sqlmonster.comOn Mar 1, 1:39 pm, "fnadal via SQLMonster.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over a
> million cpu and continued to grow until I stopped and restarted the the pull
> subscription agent on the distribution server. Then it went down to about a
> hundred cpu. As I'm writing this article its already up to three thousand cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.sqlmonster.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?|||The cpu usage. When I do a select spid,loginame,program_name, cpu from master.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million for
that agent.
Tracy McKibben wrote:
>> We have transactional replication set up. The agent is running on the
>> subscriber. However the CPU continues to grow on the subscriber. Yesterday
>[quoted text clipped - 9 lines]
>> --
>> Message posted viahttp://www.sqlmonster.com
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
--
Message posted via http://www.sqlmonster.com|||That is a cumulative value since the connection started, not an immediate
usage value.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via SQLMonster.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
>> We have transactional replication set up. The agent is running on the
>> subscriber. However the CPU continues to grow on the subscriber.
>> Yesterday
>>[quoted text clipped - 9 lines]
>> --
>> Message posted viahttp://www.sqlmonster.com
>>Can you explain a little more clearly? Exactly what statistic are you
>>looking at? What value is growing?
> --
> Message posted via http://www.sqlmonster.com
>|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:
>That is a cumulative value since the connection started, not an immediate
>usage value.
>> The cpu usage. When I do a select spid,loginame,program_name, cpu from
>> master.
>[quoted text clipped - 12 lines]
>>Can you explain a little more clearly? Exactly what statistic are you
>>looking at? What value is growing?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cpu.
Is there a profile setting that I'm missing?
Thanks all in advance!!
--
Message posted via http://www.sqlmonster.comOn Mar 1, 1:39 pm, "fnadal via SQLMonster.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over a
> million cpu and continued to grow until I stopped and restarted the the pull
> subscription agent on the distribution server. Then it went down to about a
> hundred cpu. As I'm writing this article its already up to three thousand cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.sqlmonster.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?|||The cpu usage. When I do a select spid,loginame,program_name, cpu from master.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million for
that agent.
Tracy McKibben wrote:
>> We have transactional replication set up. The agent is running on the
>> subscriber. However the CPU continues to grow on the subscriber. Yesterday
>[quoted text clipped - 9 lines]
>> --
>> Message posted viahttp://www.sqlmonster.com
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
--
Message posted via http://www.sqlmonster.com|||That is a cumulative value since the connection started, not an immediate
usage value.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via SQLMonster.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
>> We have transactional replication set up. The agent is running on the
>> subscriber. However the CPU continues to grow on the subscriber.
>> Yesterday
>>[quoted text clipped - 9 lines]
>> --
>> Message posted viahttp://www.sqlmonster.com
>>Can you explain a little more clearly? Exactly what statistic are you
>>looking at? What value is growing?
> --
> Message posted via http://www.sqlmonster.com
>|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:
>That is a cumulative value since the connection started, not an immediate
>usage value.
>> The cpu usage. When I do a select spid,loginame,program_name, cpu from
>> master.
>[quoted text clipped - 12 lines]
>>Can you explain a little more clearly? Exactly what statistic are you
>>looking at? What value is growing?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1
Friday, March 23, 2012
replication conflict error.. how to add datas to publisher ....
Hi..
I have configured publisher, distributer,subscriber... and tried to replicate it... it has done successfully...
When i try to add datas to the publisher ... it says
"conflict error"
can you please tell me how to check the replication is successfull or not.
and i want to add datas to publisher so that it should frequently updated in subscriber...
You should start by reading Books Online topic "How Merge Replication Detects and Resolves Conflicts". You can also read Replication topics about merge replication in general to get a better undestanding about how it works and how it's best used.sqlReplication changing PK
I have a very strange thing happening where the primary key field is getting
changed when synchronizing with a subscriber. Background:
-Using SQL 2k and merge replication
-Testing with Publisher and Distributor on same server.
-Setup only 1 subscriber to test.
-Added a record into the Publisher into 2 tables (People and ApplicantInfo)
with a PK-FK link (1 to 1) on a field named PersonID. I also entered 9
records into a table with 1-many relationship to the ApplicantInfo table
(but not really relevant here).
-I check the records in the tables before I synchronized and both had a key
value of 195134582.
-I then synchronized from the subscriber and got the following conflict
error:
"The row was inserted at 'LIFEDEVTEST.MCFIData' but could not be inserted at
'DELLGX260.MCFIData'. The record can't be added or changed. Referential
integrity rules require a related record in table 'People'."
-I then opened EM and searched the People table on the Publisher and the
PersonID now has a value of 211587197.
-There is no update trigger on the People table, only delete trigger and
insert trigger. Below is the insert trigger on the People table. Could it
somehow affect the PersonID when inserting into subscriber? I hope not.
CREATE TRIGGER T_People_ITrig ON dbo.People FOR INSERT AS
SET NOCOUNT ON
DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
/* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'PersonID' */
SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
SELECT @.newc = (SELECT PersonID FROM inserted)
UPDATE People SET PersonID = @.randc WHERE PersonID = @.newc
Can anyone shed light on this as it is critical to implementing replication.
Thank you.
David
Turns out, the problem had to be the trigger as it fired again when synching
and changed the PersonID again. I removed the trigger and defaulted the
PersonID to random number and now it works fine.
David
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:OA4dtoDJGHA.3120@.TK2MSFTNGP10.phx.gbl...
>I have a very strange thing happening where the primary key field is
>getting changed when synchronizing with a subscriber. Background:
> -Using SQL 2k and merge replication
> -Testing with Publisher and Distributor on same server.
> -Setup only 1 subscriber to test.
> -Added a record into the Publisher into 2 tables (People and
> ApplicantInfo) with a PK-FK link (1 to 1) on a field named PersonID. I
> also entered 9 records into a table with 1-many relationship to the
> ApplicantInfo table (but not really relevant here).
> -I check the records in the tables before I synchronized and both had a
> key value of 195134582.
> -I then synchronized from the subscriber and got the following conflict
> error:
> "The row was inserted at 'LIFEDEVTEST.MCFIData' but could not be inserted
> at 'DELLGX260.MCFIData'. The record can't be added or changed. Referential
> integrity rules require a related record in table 'People'."
> -I then opened EM and searched the People table on the Publisher and the
> PersonID now has a value of 211587197.
> -There is no update trigger on the People table, only delete trigger and
> insert trigger. Below is the insert trigger on the People table. Could
> it somehow affect the PersonID when inserting into subscriber? I hope
> not.
> CREATE TRIGGER T_People_ITrig ON dbo.People FOR INSERT AS
> SET NOCOUNT ON
> DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
> /* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'PersonID' */
> SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
> SELECT @.newc = (SELECT PersonID FROM inserted)
> UPDATE People SET PersonID = @.randc WHERE PersonID = @.newc
>
> Can anyone shed light on this as it is critical to implementing
> replication. Thank you.
>
> David
>
|||This is actually a trigger ordering issue. Merge triggers are system
triggers and fire first. Than means your insert hit and fired the merge
trigger. Your trigger then fired causing an update to the same row which
was inserted. This will almost always cause a conflict to be thrown.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:epRwmORJGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Turns out, the problem had to be the trigger as it fired again when
> synching and changed the PersonID again. I removed the trigger and
> defaulted the PersonID to random number and now it works fine.
> David
> "David Chase" <dlchase@.lifetimeinc.com> wrote in message
> news:OA4dtoDJGHA.3120@.TK2MSFTNGP10.phx.gbl...
>
changed when synchronizing with a subscriber. Background:
-Using SQL 2k and merge replication
-Testing with Publisher and Distributor on same server.
-Setup only 1 subscriber to test.
-Added a record into the Publisher into 2 tables (People and ApplicantInfo)
with a PK-FK link (1 to 1) on a field named PersonID. I also entered 9
records into a table with 1-many relationship to the ApplicantInfo table
(but not really relevant here).
-I check the records in the tables before I synchronized and both had a key
value of 195134582.
-I then synchronized from the subscriber and got the following conflict
error:
"The row was inserted at 'LIFEDEVTEST.MCFIData' but could not be inserted at
'DELLGX260.MCFIData'. The record can't be added or changed. Referential
integrity rules require a related record in table 'People'."
-I then opened EM and searched the People table on the Publisher and the
PersonID now has a value of 211587197.
-There is no update trigger on the People table, only delete trigger and
insert trigger. Below is the insert trigger on the People table. Could it
somehow affect the PersonID when inserting into subscriber? I hope not.
CREATE TRIGGER T_People_ITrig ON dbo.People FOR INSERT AS
SET NOCOUNT ON
DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
/* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'PersonID' */
SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
SELECT @.newc = (SELECT PersonID FROM inserted)
UPDATE People SET PersonID = @.randc WHERE PersonID = @.newc
Can anyone shed light on this as it is critical to implementing replication.
Thank you.
David
Turns out, the problem had to be the trigger as it fired again when synching
and changed the PersonID again. I removed the trigger and defaulted the
PersonID to random number and now it works fine.
David
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:OA4dtoDJGHA.3120@.TK2MSFTNGP10.phx.gbl...
>I have a very strange thing happening where the primary key field is
>getting changed when synchronizing with a subscriber. Background:
> -Using SQL 2k and merge replication
> -Testing with Publisher and Distributor on same server.
> -Setup only 1 subscriber to test.
> -Added a record into the Publisher into 2 tables (People and
> ApplicantInfo) with a PK-FK link (1 to 1) on a field named PersonID. I
> also entered 9 records into a table with 1-many relationship to the
> ApplicantInfo table (but not really relevant here).
> -I check the records in the tables before I synchronized and both had a
> key value of 195134582.
> -I then synchronized from the subscriber and got the following conflict
> error:
> "The row was inserted at 'LIFEDEVTEST.MCFIData' but could not be inserted
> at 'DELLGX260.MCFIData'. The record can't be added or changed. Referential
> integrity rules require a related record in table 'People'."
> -I then opened EM and searched the People table on the Publisher and the
> PersonID now has a value of 211587197.
> -There is no update trigger on the People table, only delete trigger and
> insert trigger. Below is the insert trigger on the People table. Could
> it somehow affect the PersonID when inserting into subscriber? I hope
> not.
> CREATE TRIGGER T_People_ITrig ON dbo.People FOR INSERT AS
> SET NOCOUNT ON
> DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
> /* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'PersonID' */
> SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
> SELECT @.newc = (SELECT PersonID FROM inserted)
> UPDATE People SET PersonID = @.randc WHERE PersonID = @.newc
>
> Can anyone shed light on this as it is critical to implementing
> replication. Thank you.
>
> David
>
|||This is actually a trigger ordering issue. Merge triggers are system
triggers and fire first. Than means your insert hit and fired the merge
trigger. Your trigger then fired causing an update to the same row which
was inserted. This will almost always cause a conflict to be thrown.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:epRwmORJGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Turns out, the problem had to be the trigger as it fired again when
> synching and changed the PersonID again. I removed the trigger and
> defaulted the PersonID to random number and now it works fine.
> David
> "David Chase" <dlchase@.lifetimeinc.com> wrote in message
> news:OA4dtoDJGHA.3120@.TK2MSFTNGP10.phx.gbl...
>
Replication Chain Problem
Is it possible to setup a merge replication chain where you have a Head
Office (HO) which is a publisher to a Region Office (RO) subscriber which is
a publisher to a Store Office (SO) subscriber where the data travels both
directions fully? eg. HO<->RO<->SO.
From testing, it appears that if data is changed at the SO, then it only
gets merged to the RO, not the HO as well.
Do anyone know what needs to be done to get it also merged to the HO as well?
this should work. As long as all the downstream subscribers have a lower
priority than the upstream publisher/subscriber the data should move as you
desire. You might want to check to make sure that the missing data isn't
logged in the conflict tables.
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
"Cheval" <Cheval@.discussions.microsoft.com> wrote in message
news:8D8A9DE5-B207-4CF2-997C-5BD65A3EDD01@.microsoft.com...
> Is it possible to setup a merge replication chain where you have a Head
> Office (HO) which is a publisher to a Region Office (RO) subscriber which
> is
> a publisher to a Store Office (SO) subscriber where the data travels both
> directions fully? eg. HO<->RO<->SO.
> From testing, it appears that if data is changed at the SO, then it only
> gets merged to the RO, not the HO as well.
> Do anyone know what needs to be done to get it also merged to the HO as
> well?
|||No issues. I've built these as deep as 16 levels with data flowing in both
directions.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Cheval" <Cheval@.discussions.microsoft.com> wrote in message
news:8D8A9DE5-B207-4CF2-997C-5BD65A3EDD01@.microsoft.com...
> Is it possible to setup a merge replication chain where you have a Head
> Office (HO) which is a publisher to a Region Office (RO) subscriber which
> is
> a publisher to a Store Office (SO) subscriber where the data travels both
> directions fully? eg. HO<->RO<->SO.
> From testing, it appears that if data is changed at the SO, then it only
> gets merged to the RO, not the HO as well.
> Do anyone know what needs to be done to get it also merged to the HO as
> well?
Office (HO) which is a publisher to a Region Office (RO) subscriber which is
a publisher to a Store Office (SO) subscriber where the data travels both
directions fully? eg. HO<->RO<->SO.
From testing, it appears that if data is changed at the SO, then it only
gets merged to the RO, not the HO as well.
Do anyone know what needs to be done to get it also merged to the HO as well?
this should work. As long as all the downstream subscribers have a lower
priority than the upstream publisher/subscriber the data should move as you
desire. You might want to check to make sure that the missing data isn't
logged in the conflict tables.
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
"Cheval" <Cheval@.discussions.microsoft.com> wrote in message
news:8D8A9DE5-B207-4CF2-997C-5BD65A3EDD01@.microsoft.com...
> Is it possible to setup a merge replication chain where you have a Head
> Office (HO) which is a publisher to a Region Office (RO) subscriber which
> is
> a publisher to a Store Office (SO) subscriber where the data travels both
> directions fully? eg. HO<->RO<->SO.
> From testing, it appears that if data is changed at the SO, then it only
> gets merged to the RO, not the HO as well.
> Do anyone know what needs to be done to get it also merged to the HO as
> well?
|||No issues. I've built these as deep as 16 levels with data flowing in both
directions.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Cheval" <Cheval@.discussions.microsoft.com> wrote in message
news:8D8A9DE5-B207-4CF2-997C-5BD65A3EDD01@.microsoft.com...
> Is it possible to setup a merge replication chain where you have a Head
> Office (HO) which is a publisher to a Region Office (RO) subscriber which
> is
> a publisher to a Store Office (SO) subscriber where the data travels both
> directions fully? eg. HO<->RO<->SO.
> From testing, it appears that if data is changed at the SO, then it only
> gets merged to the RO, not the HO as well.
> Do anyone know what needs to be done to get it also merged to the HO as
> well?
Replication between SQL Server 2000 and SQL Server 2005
Do you know if it is possible to synchronize a database in SQL Server 2000 SP3a (Publisher) and a database in SQL Server 2005 (Subscriber)?
Has anyone tried it? What are the most common problems you faced? Are there many differences from the Replication process from SQL Server 2000 (publisher) to SQL Server 2000 (subscriber)?
Thanks Very Much
Yes for transactional replication, no for merge replication. Since you're limited to functionality of a SQL 2000 publication, you won't gain much in terms of replication with a SQL 2005 subscriber. But if you use your subscriber for other purposes, like reporting, then you get to take advantage of SQL 2005 features there.|||Is there anything special you are doing to setup replication between SQL Server 2000 SP3(a) and SQL Server 2005 SP1? Both are enterprise versions and I am using transactional replication.
So far, I have not been able to make replication work. Using the same SQL 2K database and replicationg to another SQL 2K database, replication worked fine.
I just cannt seem to get SQL 2K to publish and SQL 2L5 to subscribe.
Is there something I am overlooking?
Thanks,
Roy
|||Is there an error you're getting?|||Not sure if this is the issue you hit:
Make sure to use SQL 2005 Management studio to create publication and add subscription for SQL 2000 publisher, you can not connect to SQL 2005 from SQL 2000 Enterprise manager thus will not be able to add SQL 2005 subscription from SQL 2000 enterprise manager.
Or you can TSQL script to setup replication programmatically.
Thanks,
Zhiqiang Feng
|||Does the SQL Server 2005 server have o be the distributor? I tried creating the distributor using SS 2K5 and was messaged that a subscription could not be created by 2005 on an older (2000) server.
Am I supposed to create the distributor and publisher using 2000 and the subscriber using 2005?
I really appreciate any and all help/advice
Roy
|||For transactional replication, you can have SQL 2000 sp3+ publisher/distributor with SQL 2005 subscriber. But for merge replication, you must have distributor >= publisher >= subscriber, from your original posting, seems like you're using transactional replication, right?
By the way, what's the version number of your SQL 2000 publisher? (8.00.760 or up?)
Can you describe step by step what you did and exactly what error you're getting?
I just went through the process of setup SQL 2000 publisher & distributor from SQL 2005 management studio and didn't hit any issues.
Thanks,
Zhiqiang Feng
|||MY SQL Server 2000 version number is 8.0.818
I went to the publisher server (mase), it is SQL2K and created the distributor, then the publisher. However, one thing that makes me wonder is having to check the box Server SQL Server 2000 on the form that is requesting what type of server will be subscribing. Obviously, 2K came before 2005 and did not have a box for 2005. Is the 2000 check box what I need to check?
I will post the rest of the the steps as I go through them.
Thanks a lot for your help.
Roy
|||If you create SQL 2000 tran publication from SQL 2000 Enterprise manager, yes, it doesn't know SQL 2005 so you have to pick the SQL 2000 option for subscription, but that doesn't prevent you from adding a SQL 2005 subscriber from SQL 2005 mgmt studio which is officially supported. However, if you create SQL 2000 tran publication from SQL 2005 mgmt studio (use mgmt studio connecting to the remote SQL 2000 box), you will not see that prompt. That's why I recommend you setup everything from SQL 2005 management studio for the SQL 2000 publisher/distributor.
Thanks,
Zhiqiang Feng
|||When I attempt to create a publisher using SS2K5, on SS 2K, I get a message saying the server 'mase' is an older version of SQL Server and cannot be the Distributor for server 'sql2'.
Maybe this is my problem, does the distributor need to be on SS2K5?
Also, to create a publisher on a SS2K server using SS2K5 Management Studio do you right clisck on Local Publication?
I created the subscriber using SS2K5 and all looks good. When I right click the subscriber and click View Synchronization Status I get this message:
The job failed. The Job was invoked by User sa. The last step to run was step 1 (Run agent.).
When I look at History I see this message: Message
Unable to start execution of step 1 (reason: Error authenticating proxy PMS\svcsqladmin, system error: Logon failure: unknown user name or bad password.). The step failed.
I know the password is correct for this login as we tested it just before attempting to create replication.
Is there anyyhnig I am doing incorrectly? I would love to get this set up. On top of everything else, this is the first replication I have ever tried to configure.
Thanks again,
Roy
|||hi,
right now I facing the same problem.
you have said that the only thing that work is using transactional replication.
the problem is my db don't have primary key.
do you have other option, so we can have the same or at least munites delay database.
please advice
thanks
Replication between SQL Server 2000 and SQL Server 2005
Do you know if it is possible to synchronize a database in SQL Server 2000 SP3a (Publisher) and a database in SQL Server 2005 (Subscriber)?
Has anyone tried it? What are the most common problems you faced? Are there many differences from the Replication process from SQL Server 2000 (publisher) to SQL Server 2000 (subscriber)?
Thanks Very Much
Yes for transactional replication, no for merge replication. Since you're limited to functionality of a SQL 2000 publication, you won't gain much in terms of replication with a SQL 2005 subscriber. But if you use your subscriber for other purposes, like reporting, then you get to take advantage of SQL 2005 features there.|||
Is there anything special you are doing to setup replication between SQL Server 2000 SP3(a) and SQL Server 2005 SP1? Both are enterprise versions and I am using transactional replication.
So far, I have not been able to make replication work. Using the same SQL 2K database and replicationg to another SQL 2K database, replication worked fine.
I just cannt seem to get SQL 2K to publish and SQL 2L5 to subscribe.
Is there something I am overlooking?
Thanks,
Roy
|||Is there an error you're getting?|||Not sure if this is the issue you hit:
Make sure to use SQL 2005 Management studio to create publication and add subscription for SQL 2000 publisher, you can not connect to SQL 2005 from SQL 2000 Enterprise manager thus will not be able to add SQL 2005 subscription from SQL 2000 enterprise manager.
Or you can TSQL script to setup replication programmatically.
Thanks,
Zhiqiang Feng
|||
Does the SQL Server 2005 server have o be the distributor? I tried creating the distributor using SS 2K5 and was messaged that a subscription could not be created by 2005 on an older (2000) server.
Am I supposed to create the distributor and publisher using 2000 and the subscriber using 2005?
I really appreciate any and all help/advice
Roy
|||For transactional replication, you can have SQL 2000 sp3+ publisher/distributor with SQL 2005 subscriber. But for merge replication, you must have distributor >= publisher >= subscriber, from your original posting, seems like you're using transactional replication, right?
By the way, what's the version number of your SQL 2000 publisher? (8.00.760 or up?)
Can you describe step by step what you did and exactly what error you're getting?
I just went through the process of setup SQL 2000 publisher & distributor from SQL 2005 management studio and didn't hit any issues.
Thanks,
Zhiqiang Feng
|||
MY SQL Server 2000 version number is 8.0.818
I went to the publisher server (mase), it is SQL2K and created the distributor, then the publisher. However, one thing that makes me wonder is having to check the box Server SQL Server 2000 on the form that is requesting what type of server will be subscribing. Obviously, 2K came before 2005 and did not have a box for 2005. Is the 2000 check box what I need to check?
I will post the rest of the the steps as I go through them.
Thanks a lot for your help.
Roy
|||If you create SQL 2000 tran publication from SQL 2000 Enterprise manager, yes, it doesn't know SQL 2005 so you have to pick the SQL 2000 option for subscription, but that doesn't prevent you from adding a SQL 2005 subscriber from SQL 2005 mgmt studio which is officially supported. However, if you create SQL 2000 tran publication from SQL 2005 mgmt studio (use mgmt studio connecting to the remote SQL 2000 box), you will not see that prompt. That's why I recommend you setup everything from SQL 2005 management studio for the SQL 2000 publisher/distributor.
Thanks,
Zhiqiang Feng
|||When I attempt to create a publisher using SS2K5, on SS 2K, I get a message saying the server 'mase' is an older version of SQL Server and cannot be the Distributor for server 'sql2'.
Maybe this is my problem, does the distributor need to be on SS2K5?
Also, to create a publisher on a SS2K server using SS2K5 Management Studio do you right clisck on Local Publication?
I created the subscriber using SS2K5 and all looks good. When I right click the subscriber and click View Synchronization Status I get this message:
The job failed. The Job was invoked by User sa. The last step to run was step 1 (Run agent.).
When I look at History I see this message: Message
Unable to start execution of step 1 (reason: Error authenticating proxy PMS\svcsqladmin, system error: Logon failure: unknown user name or bad password.). The step failed.
I know the password is correct for this login as we tested it just before attempting to create replication.
Is there anyyhnig I am doing incorrectly? I would love to get this set up. On top of everything else, this is the first replication I have ever tried to configure.
Thanks again,
Roy
|||hi,
right now I facing the same problem.
you have said that the only thing that work is using transactional replication.
the problem is my db don't have primary key.
do you have other option, so we can have the same or at least munites delay database.
please advice
thanks
sqlReplication between SQL Server 2000 and SQL Server 2005
Do you know if it is possible to synchronize a database in SQL Server 2000 SP3a (Publisher) and a database in SQL Server 2005 (Subscriber)?
Has anyone tried it? What are the most common problems you faced? Are there many differences from the Replication process from SQL Server 2000 (publisher) to SQL Server 2000 (subscriber)?
Thanks Very Much
Yes for transactional replication, no for merge replication. Since you're limited to functionality of a SQL 2000 publication, you won't gain much in terms of replication with a SQL 2005 subscriber. But if you use your subscriber for other purposes, like reporting, then you get to take advantage of SQL 2005 features there.|||Is there anything special you are doing to setup replication between SQL Server 2000 SP3(a) and SQL Server 2005 SP1? Both are enterprise versions and I am using transactional replication.
So far, I have not been able to make replication work. Using the same SQL 2K database and replicationg to another SQL 2K database, replication worked fine.
I just cannt seem to get SQL 2K to publish and SQL 2L5 to subscribe.
Is there something I am overlooking?
Thanks,
Roy
|||Is there an error you're getting?|||Not sure if this is the issue you hit:
Make sure to use SQL 2005 Management studio to create publication and add subscription for SQL 2000 publisher, you can not connect to SQL 2005 from SQL 2000 Enterprise manager thus will not be able to add SQL 2005 subscription from SQL 2000 enterprise manager.
Or you can TSQL script to setup replication programmatically.
Thanks,
Zhiqiang Feng
|||Does the SQL Server 2005 server have o be the distributor? I tried creating the distributor using SS 2K5 and was messaged that a subscription could not be created by 2005 on an older (2000) server.
Am I supposed to create the distributor and publisher using 2000 and the subscriber using 2005?
I really appreciate any and all help/advice
Roy
|||For transactional replication, you can have SQL 2000 sp3+ publisher/distributor with SQL 2005 subscriber. But for merge replication, you must have distributor >= publisher >= subscriber, from your original posting, seems like you're using transactional replication, right?
By the way, what's the version number of your SQL 2000 publisher? (8.00.760 or up?)
Can you describe step by step what you did and exactly what error you're getting?
I just went through the process of setup SQL 2000 publisher & distributor from SQL 2005 management studio and didn't hit any issues.
Thanks,
Zhiqiang Feng
|||MY SQL Server 2000 version number is 8.0.818
I went to the publisher server (mase), it is SQL2K and created the distributor, then the publisher. However, one thing that makes me wonder is having to check the box Server SQL Server 2000 on the form that is requesting what type of server will be subscribing. Obviously, 2K came before 2005 and did not have a box for 2005. Is the 2000 check box what I need to check?
I will post the rest of the the steps as I go through them.
Thanks a lot for your help.
Roy
|||If you create SQL 2000 tran publication from SQL 2000 Enterprise manager, yes, it doesn't know SQL 2005 so you have to pick the SQL 2000 option for subscription, but that doesn't prevent you from adding a SQL 2005 subscriber from SQL 2005 mgmt studio which is officially supported. However, if you create SQL 2000 tran publication from SQL 2005 mgmt studio (use mgmt studio connecting to the remote SQL 2000 box), you will not see that prompt. That's why I recommend you setup everything from SQL 2005 management studio for the SQL 2000 publisher/distributor.
Thanks,
Zhiqiang Feng
|||When I attempt to create a publisher using SS2K5, on SS 2K, I get a message saying the server 'mase' is an older version of SQL Server and cannot be the Distributor for server 'sql2'.
Maybe this is my problem, does the distributor need to be on SS2K5?
Also, to create a publisher on a SS2K server using SS2K5 Management Studio do you right clisck on Local Publication?
I created the subscriber using SS2K5 and all looks good. When I right click the subscriber and click View Synchronization Status I get this message:
The job failed. The Job was invoked by User sa. The last step to run was step 1 (Run agent.).
When I look at History I see this message: Message
Unable to start execution of step 1 (reason: Error authenticating proxy PMS\svcsqladmin, system error: Logon failure: unknown user name or bad password.). The step failed.
I know the password is correct for this login as we tested it just before attempting to create replication.
Is there anyyhnig I am doing incorrectly? I would love to get this set up. On top of everything else, this is the first replication I have ever tried to configure.
Thanks again,
Roy
|||hi,
right now I facing the same problem.
you have said that the only thing that work is using transactional replication.
the problem is my db don't have primary key.
do you have other option, so we can have the same or at least munites delay database.
please advice
thanks
Subscribe to:
Posts (Atom)