Hi All,
On a server I configured publication of a database and push subcriptions
successfully using Enterprise Manager. But later when I select the
"Configure Publishing, Subsribers and Distribution" option again by either
right clicking on Replication folder or Menu, I find Subscribers tab is
missing, I see only Distributor and Publishers tabs.
Can anyone please tell me what I am missing anything here?
Thanks a lot,
VM
The server is not configured as a publisher. Enable it as a publisher and
click apply and ok. Reopen this dialog.
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
"VM" <VM@.discussions.microsoft.com> wrote in message
news:8C3C9EA9-B273-4CA6-99BF-CA51B6E25294@.microsoft.com...
> Hi All,
> On a server I configured publication of a database and push subcriptions
> successfully using Enterprise Manager. But later when I select the
> "Configure Publishing, Subsribers and Distribution" option again by
> either
> right clicking on Replication folder or Menu, I find Subscribers tab is
> missing, I see only Distributor and Publishers tabs.
> Can anyone please tell me what I am missing anything here?
> Thanks a lot,
> VM
Showing posts with label subscriber. Show all posts
Showing posts with label subscriber. Show all posts
Monday, March 12, 2012
Wednesday, March 7, 2012
Missing replicated records
Hi gurus there,
I have a puzzling scenario here.
Environment: SQL Server 2K5 (sp2) EE + windows 2K3
I have a publisher server PubSrv_1and two subscriber severs SubSrv_1 and
SubSrv_2, there are two publications on the Publication_1, and
Publication_2, but they all contain the same table as article tbl_A
Publication_1 is a transational replication with Subscription on SubSrv_1
and Publication_2 is a transactional replication with updateable
subscription on SubSrv_2.
Issue: sometimes I find there are missing records which appear in tbl_A on
PubSrv_1 but not in tbl_A on SubSrv_2 while still in tbl_A on SubSrv_1. In
another word, some records in the publication table are NOT replicated to
one subscriber but still replicated to another subscriber.
I am confused how this happens. Could someone please shed some lights here?
TIA
Jeff
Can you check the conflicts log on the subscriber to see if the
missing rows are logged there?
On Jan 9, 3:03 am, "jeff_y" <jeffrey...@.abc.com> wrote:
> Hi gurus there,
> I have a puzzling scenario here.
> Environment: SQL Server 2K5 (sp2) EE + windows 2K3
> I have a publisher server PubSrv_1and two subscriber severs SubSrv_1 and
> SubSrv_2, there are two publications on the Publication_1, and
> Publication_2, but they all contain the same table as article tbl_A
> Publication_1 is a transational replication with Subscription on SubSrv_1
> and Publication_2 is a transactional replication with updateable
> subscription on SubSrv_2.
> Issue: sometimes I find there are missing records which appear in tbl_A on
> PubSrv_1 but not in tbl_A on SubSrv_2 while still in tbl_A on SubSrv_1. In
> another word, some records in the publication table are NOT replicated to
> one subscriber but still replicated to another subscriber.
> I am confused how this happens. Could someone please shed some lights here?
> TIA
> Jeff
|||Hi Hillary,
Thanks for your quick response.
I am not sure where the conflicts log are for the transactional replication.
More information:
I have even put a delete trigger on the problematic table at the subsriber
side to try to log any deletion on the table, but find the trigger has never
been fired off. So in another word, the missing records have never been
deleted as they were in fact never replicated over from the publisher side.
I find the two subscribers have different editions, the SubSrv_2, which has
seen the issues, has edition 3042, while SubSrv_1 has 3161. Do you think
this can cause the issue (I am not convinced though)?
Thanks,
Jeff
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:86aa0601-0caa-49ad-b9a1-d5d3cc732456@.f10g2000hsf.googlegroups.com...
> Can you check the conflicts log on the subscriber to see if the
> missing rows are logged there?
> On Jan 9, 3:03 am, "jeff_y" <jeffrey...@.abc.com> wrote:
>
I have a puzzling scenario here.
Environment: SQL Server 2K5 (sp2) EE + windows 2K3
I have a publisher server PubSrv_1and two subscriber severs SubSrv_1 and
SubSrv_2, there are two publications on the Publication_1, and
Publication_2, but they all contain the same table as article tbl_A
Publication_1 is a transational replication with Subscription on SubSrv_1
and Publication_2 is a transactional replication with updateable
subscription on SubSrv_2.
Issue: sometimes I find there are missing records which appear in tbl_A on
PubSrv_1 but not in tbl_A on SubSrv_2 while still in tbl_A on SubSrv_1. In
another word, some records in the publication table are NOT replicated to
one subscriber but still replicated to another subscriber.
I am confused how this happens. Could someone please shed some lights here?
TIA
Jeff
Can you check the conflicts log on the subscriber to see if the
missing rows are logged there?
On Jan 9, 3:03 am, "jeff_y" <jeffrey...@.abc.com> wrote:
> Hi gurus there,
> I have a puzzling scenario here.
> Environment: SQL Server 2K5 (sp2) EE + windows 2K3
> I have a publisher server PubSrv_1and two subscriber severs SubSrv_1 and
> SubSrv_2, there are two publications on the Publication_1, and
> Publication_2, but they all contain the same table as article tbl_A
> Publication_1 is a transational replication with Subscription on SubSrv_1
> and Publication_2 is a transactional replication with updateable
> subscription on SubSrv_2.
> Issue: sometimes I find there are missing records which appear in tbl_A on
> PubSrv_1 but not in tbl_A on SubSrv_2 while still in tbl_A on SubSrv_1. In
> another word, some records in the publication table are NOT replicated to
> one subscriber but still replicated to another subscriber.
> I am confused how this happens. Could someone please shed some lights here?
> TIA
> Jeff
|||Hi Hillary,
Thanks for your quick response.
I am not sure where the conflicts log are for the transactional replication.
More information:
I have even put a delete trigger on the problematic table at the subsriber
side to try to log any deletion on the table, but find the trigger has never
been fired off. So in another word, the missing records have never been
deleted as they were in fact never replicated over from the publisher side.
I find the two subscribers have different editions, the SubSrv_2, which has
seen the issues, has edition 3042, while SubSrv_1 has 3161. Do you think
this can cause the issue (I am not convinced though)?
Thanks,
Jeff
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:86aa0601-0caa-49ad-b9a1-d5d3cc732456@.f10g2000hsf.googlegroups.com...
> Can you check the conflicts log on the subscriber to see if the
> missing rows are logged there?
> On Jan 9, 3:03 am, "jeff_y" <jeffrey...@.abc.com> wrote:
>
missing records on subscribing database (transactional replication)
Hi all,
I have a publishing database and a subscriber database on two
different machines. Transactional replication is configured between
them. Everything is straigforward at the start, then after a few days
I got reports that the same tables on both databases are not in synch,
and some tables in the subscriber database has missing rows.
Has anyone experienced this? I realize that it is possible to delete
rows on the subscriber database, but other than that, is it possible
for the transactional replication to actually fail to copy some rows
from the publishing database?
There are no filters set, btw.
Thanks!
Aramid
If you don't have any errors in the replication engine, then, no it will not
fail to send changes. You would have to interfere with it in some way such
as within the distribution database. I would suggest doing some auditing at
your subscriber and see if there is a process which is making changes there.
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.
"Aramid" <aramid@.hotmail.com> wrote in message
news:8fueu1to6vadlh5dd4q1be9509cteqnbdk@.4ax.com...
> Hi all,
> I have a publishing database and a subscriber database on two
> different machines. Transactional replication is configured between
> them. Everything is straigforward at the start, then after a few days
> I got reports that the same tables on both databases are not in synch,
> and some tables in the subscriber database has missing rows.
> Has anyone experienced this? I realize that it is possible to delete
> rows on the subscriber database, but other than that, is it possible
> for the transactional replication to actually fail to copy some rows
> from the publishing database?
> There are no filters set, btw.
> Thanks!
> Aramid
|||Aramid,
these are 2 separate possibilities that you're describing. In one, the rows
are deleted from the subscriber, while in the other, some inserts are not
sent from the publisher to the subscriber. For the first, this is unlikely
to occur through the replication engine, so I'd go along with Mike's
suggestion and use Lumigent's LogExplorer to investigate. This is also
possible to occur naturally through the replication, if you are replicating
stored procedure execution. In the other case, I'd use sp_browsereplcmds to
see if the commands are still waiting to be sent down.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
I have a publishing database and a subscriber database on two
different machines. Transactional replication is configured between
them. Everything is straigforward at the start, then after a few days
I got reports that the same tables on both databases are not in synch,
and some tables in the subscriber database has missing rows.
Has anyone experienced this? I realize that it is possible to delete
rows on the subscriber database, but other than that, is it possible
for the transactional replication to actually fail to copy some rows
from the publishing database?
There are no filters set, btw.
Thanks!
Aramid
If you don't have any errors in the replication engine, then, no it will not
fail to send changes. You would have to interfere with it in some way such
as within the distribution database. I would suggest doing some auditing at
your subscriber and see if there is a process which is making changes there.
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.
"Aramid" <aramid@.hotmail.com> wrote in message
news:8fueu1to6vadlh5dd4q1be9509cteqnbdk@.4ax.com...
> Hi all,
> I have a publishing database and a subscriber database on two
> different machines. Transactional replication is configured between
> them. Everything is straigforward at the start, then after a few days
> I got reports that the same tables on both databases are not in synch,
> and some tables in the subscriber database has missing rows.
> Has anyone experienced this? I realize that it is possible to delete
> rows on the subscriber database, but other than that, is it possible
> for the transactional replication to actually fail to copy some rows
> from the publishing database?
> There are no filters set, btw.
> Thanks!
> Aramid
|||Aramid,
these are 2 separate possibilities that you're describing. In one, the rows
are deleted from the subscriber, while in the other, some inserts are not
sent from the publisher to the subscriber. For the first, this is unlikely
to occur through the replication engine, so I'd go along with Mike's
suggestion and use Lumigent's LogExplorer to investigate. This is also
possible to occur naturally through the replication, if you are replicating
stored procedure execution. In the other case, I'd use sp_browsereplcmds to
see if the commands are still waiting to be sent down.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Subscribe to:
Posts (Atom)