Confused about snapshot repl

If I have applied a database dump to the subscriber for a no-sync database
that is using snapshot replication, do I need to keep applying new
snapshots? The distribution agents seem to be "delivering transactions" but
not as many as when I used transactional repl on the same database (this was
no-sync as well.) I haven't run any snapshots, because it says it is
delivering the transactions; not sure if this is correct.
Please help.
Thanks so much,
Kristy
Kirsty,
I'm confused and am not too sure what type of replication you are wanting to
set up. The title of the post implies snapshot, but dong a nosync
initialization for snapshot doesn't really make sense. Can you provide a
little more info on this and also what the transactions are that are being
delivered (sp_browsereplcmds).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Originally it was suppose to be transaction repl. But there were problems on
the host and the person who reset up the subscriptions accidently chose the
snapshot for the pull subscription. One of them was set to Transactional,
but it's been having major latency issues that I can't figure out. I didn't
know if the now snapshots subscriptions were not delivering everything
(because no further snapshots other than the original Db dump and snapshot -
that wasn't used because we shut down access to the db during db dump and
snapshot - has happened,) so I posted about that (see below for thread
questions.
If you never run the snapshot agent pass the first time then how come the
distribution agent looks like it is delivering transactions?
Thanks,
Kristy[vbcol=seagreen]
It only will if you do a no-sync.
Hilary Cotter[vbcol=seagreen]
So are the transactions being replicated then? Or do I have to keep running
snapshots?
Thanks,
Kristy
So that is why I thought it was no-sync. The 2 subscribing DBs do not get
updated in anyway and do not need to update the publisher. In fact, this
would be very bad. They DO need to have the lowest latency as possible. This
is a large DB (100+GB) that is a OLTP system, with broken down subscriptions
(pull) for the 1 production DB to give the info to the 2 subscribing DBs.
Not sure what you need from sp_browsereplcmds, so let me know. There is a
lot of records in there right now, but "I think" they seem to have started
from last night. Not sure if they are in order though, so I can say for
sure.
Clear as mud, right? Sorry. Let me know if you need any more info.
Thanks,
--Kristy
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eyNOUZ9UGHA.2360@.TK2MSFTNGP09.phx.gbl...
> Kirsty,
> I'm confused and am not too sure what type of replication you are wanting
to
> set up. The title of the post implies snapshot, but dong a nosync
> initialization for snapshot doesn't really make sense. Can you provide a
> little more info on this and also what the transactions are that are being
> delivered (sp_browsereplcmds).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Kirsty,
sorry but I don't follow this scenarion. To be honest I think you're getting
the terminology confused as what you're describing doesn't sound like
snapshot replication. Let's get as much systematic info as we can, so pls
can you confirm :
(a) have you set up Transactional Replication with a nosync initialization?
(b) what are the current issues you are encountering?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Okay, here is the info. I have 1 DB that is 100+ GB. It is broken down into
10 publications to try and improve latency issues (as suggested by Hiliary
awhile back ago.) Each publication is subscribed by 2 different servers;
essentially a "hot backup" and a "warm backup", though the later is to be
used for batch printing of reports as well in the near future.
Yes I was getting the terminology confused. Here is why:
When I look at my publisher and the publications in EM, they say they are
transaction replication. HOWEVER, when I run sp_helppullsubscription on both
of the subscriber DBs,
they return a publication_type of 1 (well except for one of them which
returns a 0 and is the one causing me high latency issues.) BOL says 1 =
snapshot and 0 = transactional replication. ADDitionally, if I look in EM on
the subscrtiption server under the pull subscriptions
folder of the subscribing database, they concur with the results from the
sp_helppullsubscription.
So that is why I am confused as to snapshot versus transactional. They are
suppose to be transcational.
The one (out of 20 subscriptions) that is coming up as transactional, is the
one causing me all of the problems. It has a sync type of automatic, because
when it expired because latency got too high (or was marked that it had to
be reinitialized) at that point a snapshot had to be created for that
subscription. The others have a sync_type of 2 (no sync). Whenever I run
sp_browsereplcmds, it seems like all of the outstanding transactions are
stuck in there and are not moving. So latency build up and again reaches an
unacceptable level. EM will say "delivering transactions" but I never see it
say anything else, and the commands seem to just sit in sp_browsereplcmds
result set.
The latency only goes up for this subscription, it never goes down. It just
climbs for a few days and then gets marked for reintialization (which I
would have to do anyways because I can't have a latecny of more than a few
hours.) All of my other subscriptions flux between 1 sec and 10 seconds.
Even the one that is suppose to be delivering the same subscription to a
different server.
So I am at a complete loss at this point. I don't even know if the other
subscriptions are working right since they say in sp_helppullsubscription
that they are snapshot. They are usually having commands dielivered
according to EM or are Idle. I need to figure out 1.) the others are working
right and 2.) what in the heck is wrong with the rogue subscription and how
to fix it.
I have Hiliary's book, but I can't find anything with this problem in it.
I'd sit down and cry right now if it would make me such a drama queen. ;-)
--Kristy
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:elr$CwJVGHA.5852@.TK2MSFTNGP10.phx.gbl...
> Kirsty,
> sorry but I don't follow this scenarion. To be honest I think you're
getting
> the terminology confused as what you're describing doesn't sound like
> snapshot replication. Let's get as much systematic info as we can, so pls
> can you confirm :
> (a) have you set up Transactional Replication with a nosync
initialization?
> (b) what are the current issues you are encountering?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Kristy,
please can you script out 2 pull subscriptions - one that reports that it is
transactional and the other that reports being snapshot and I'll take a
look.
Cheers,
Paul
|||Here is the one that lists as Transactional:
/****** Begin: Script to be run at Subscriber: ******/
exec sp_addpullsubscription @.publisher = N'OPT3', @.publisher_db = N'MyDB',
@.publication = N'5 - Asset', @.independent_agent = N'true',
@.subscription_type = N'pull', @.description = N'', @.update_mode = N'read
only', @.immediate_sync = 0
exec sp_addpullsubscription_agent @.publisher = N'OPT3', @.publisher_db =
N'MyDB', @.publication = N'5 - Asset', @.distributor = N'OPT3',
@.subscriber_security_mode = 1, @.distributor_security_mode = 0,
@.distributor_login = N'mine', @.distributor_password = N'', @.frequency_type =
64, @.frequency_interval = 1, @.frequency_relative_interval = 1,
@.frequency_recurrence_factor = 0, @.frequency_subday = 4,
@.frequency_subday_interval = 5, @.active_start_date = 0, @.active_end_date =
0, @.active_start_time_of_day = 0, @.active_end_time_of_day = 235959,
@.enabled_for_syncmgr = N'false', @.use_ftp = N'false', @.publication_type = 0,
@.dts_package_location = N'subscriber', @.offloadagent = N'false'
GO
/****** End: Script to be run at Subscriber: ******/

Here is the one listed as Snapshot:
/****** Begin: Script to be run at Subscriber: ******/
exec sp_addpullsubscription @.publisher = N'OPT3', @.publisher_db = N'MyDB',
@.publication = N'5 - Asset', @.independent_agent = N'true',
@.subscription_type = N'pull', @.update_mode = N'read only', @.immediate_sync =
0
exec sp_addpullsubscription_agent @.publisher = N'OPT3', @.publisher_db =
N'MyDB', @.publication = N'5 - Asset', @.distributor = N'OPT3',
@.subscriber_security_mode = 1, @.distributor_security_mode = 0,
@.distributor_login = N'mine', @.distributor_password = N'', @.frequency_type =
64, @.frequency_interval = 1, @.frequency_relative_interval = 1,
@.frequency_recurrence_factor = 0, @.frequency_subday = 4,
@.frequency_subday_interval = 5, @.active_start_date = 0, @.active_end_date =
0, @.active_start_time_of_day = 0, @.active_end_time_of_day = 235959,
@.enabled_for_syncmgr = N'false', @.use_ftp = N'false', @.publication_type = 1,
@.dts_package_location = N'subscriber', @.offloadagent = N'false'
GO
/****** End: Script to be run at Subscriber: ******/
--Kristy
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23e4uaivVGHA.4976@.TK2MSFTNGP11.phx.gbl...
> Kristy,
> please can you script out 2 pull subscriptions - one that reports that it
is
> transactional and the other that reports being snapshot and I'll take a
> look.
> Cheers,
> Paul
>
|||Kristy,
I notice that the @.publication_type = 1 is set differently - were these
created from scripts and perhaps the update was missed out?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I did a "generate script" on them from your request. They were both done
originally via Enterprise manager. THe transactional one (via
publication_type) has been redone many times because it keeps running at
high latency and I have to end up redoing it. I will just sit there and seem
not to deliver anything and just grow and grow until I have to reinitialize.
--Kristy
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OXbhTcLWGHA.3660@.TK2MSFTNGP04.phx.gbl...
> Kristy,
> I notice that the @.publication_type = 1 is set differently - were these
> created from scripts and perhaps the update was missed out?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Kristy,
please can you post up your database schema and a script to create the
publication and subscriptions and I'll try to repro.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Conflicts with Merge Replication

I am seeing the following conflict message in a merge replication
system.
Statler is the subscriber (also, remote distributor) and
EMGSQL1 is the publisher
The row was updated at Statler.Caryn but could not be updated
at emgsql1.caryn. Can not update Tlightbox because TlightboxFile
exists.
Column Conflight WinnerConflict Loser
lightbox_id19881988
member_id10531053
lb_nameCustomerCustwomer
create_dt5/13/2005 12:00:00 am5/13/2005 12:00:00 AM
last_mod_dt
expiration_dt8/11/2005 12:00:00 am8/11/2005 12:00:00 am
email_check{74434092-E95F-40B6-9211-99700DB
rowguidrowguid_valueidentical
the table definition for tlightbox is:
CREATE TABLE [dbo].[TLightBox] (
[lightbox_id] [int] IDENTITY (1, 1) NOT FOR REPLICATION NOT NULL ,
[member_id] [int] NULL ,
[lb_name] [varchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[create_dt] [datetime] NULL ,
[last_mod_dt] [datetime] NULL ,
[expiration_dt] [datetime] NULL ,
[email_check] [uniqueidentifier] NULL ,
[rowguid] uniqueidentifier ROWGUIDCOL NOT NULL
) ON [PRIMARY]
GO
CREATE TABLE [dbo].[TLightboxFile] (
[lightbox_id] [int] NOT NULL ,
[modeltalent_id] [int] NOT NULL ,
[rank] [int] NULL ,
[rowguid] uniqueidentifier ROWGUIDCOL NOT NULL
) ON [PRIMARY]
GO
These tables are on both servers.
Any Ideas?
Thanks
Dave
what is the relationship between TLightBox and TLightBoxFile?
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
"David Gresham" <gresham@.panix.com> wrote in message
news:d62p39$lks$1@.reader1.panix.com...
> I am seeing the following conflict message in a merge replication
> system.
> Statler is the subscriber (also, remote distributor) and
> EMGSQL1 is the publisher
> The row was updated at Statler.Caryn but could not be updated
> at emgsql1.caryn. Can not update Tlightbox because TlightboxFile
> exists.
> Column Conflight Winner Conflict Loser
> lightbox_id 1988 1988
> member_id 1053 1053
> lb_name Customer Custwomer
> create_dt 5/13/2005 12:00:00 am 5/13/2005 12:00:00 AM
> last_mod_dt
> expiration_dt 8/11/2005 12:00:00 am 8/11/2005 12:00:00 am
> email_check {74434092-E95F-40B6-9211-99700DB
> rowguid rowguid_value identical
>
> the table definition for tlightbox is:
> CREATE TABLE [dbo].[TLightBox] (
> [lightbox_id] [int] IDENTITY (1, 1) NOT FOR REPLICATION NOT NULL ,
> [member_id] [int] NULL ,
> [lb_name] [varchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
> [create_dt] [datetime] NULL ,
> [last_mod_dt] [datetime] NULL ,
> [expiration_dt] [datetime] NULL ,
> [email_check] [uniqueidentifier] NULL ,
> [rowguid] uniqueidentifier ROWGUIDCOL NOT NULL
> ) ON [PRIMARY]
> GO
>
> CREATE TABLE [dbo].[TLightboxFile] (
> [lightbox_id] [int] NOT NULL ,
> [modeltalent_id] [int] NOT NULL ,
> [rank] [int] NULL ,
> [rowguid] uniqueidentifier ROWGUIDCOL NOT NULL
> ) ON [PRIMARY]
> GO
>
> These tables are on both servers.
>
> Any Ideas?
> Thanks
>
> Dave
>
|||In article <ek417yCWFHA.2960@.TK2MSFTNGP15.phx.gbl>,
Hilary Cotter <hilary.cotter@.gmail.com> wrote:
>what is the relationship between TLightBox and TLightBoxFile?
>
I just looked at the tables in question and there is no
defined releationship set between them. The only relationship
defined for TlightBox was for another table called TMember
with MemberID as the relationship column.

>"David Gresham" <gresham@.panix.com> wrote in message
>news:d62p39$lks$1@.reader1.panix.com...
>
|||Just seeing if I had given you all the info you needed for
this question. This database is a legacy database where
the original developers are no longer around. There
are no fk's that would join the two tables in question.
Sincerely,
Dave Gresham
In article <ek417yCWFHA.2960@.TK2MSFTNGP15.phx.gbl>,
Hilary Cotter <hilary.cotter@.gmail.com> wrote:
>what is the relationship between TLightBox and TLightBoxFile?
>--
>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
>"David Gresham" <gresham@.panix.com> wrote in message
>news:d62p39$lks$1@.reader1.panix.com...
>
|||Your problem does not make a whole lot of sense. the best approach is to try
to repro it.
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
"David Gresham" <gresham@.panix.com> wrote in message
news:d6algu$st6$1@.reader1.panix.com...
> Just seeing if I had given you all the info you needed for
> this question. This database is a legacy database where
> the original developers are no longer around. There
> are no fk's that would join the two tables in question.
> Sincerely,
>
> Dave Gresham
>
> In article <ek417yCWFHA.2960@.TK2MSFTNGP15.phx.gbl>,
> Hilary Cotter <hilary.cotter@.gmail.com> wrote:
>

Conflicts from nowhere

I have two tables that are getting conflicts between the subscriber and the publisher, however I am pretty sure we only update these tables at the subscriber.

I have column level tracking turned on.

The tables both have Nonoverlapping, single subscription (3) set for partition options. I wonder does this do any maintenance to the tables?

I have put in place some triggers to audit what makes changes to the data, but won't know until tomorrow, so if there is something that anyone knows about that might help, please let me know.

Thanks

Hi,

Could you return the contents of MSmerge_conflicts_info and MSmerge_conflict_publication_article table for the article where the conflict occurred? Also, there are probably some information about conflict in merge agent history. Do you have some primary key, foreign key constraint on publisher only? That will cause conflict if the subscriber row violated the constraint and failed to be applied on publisher.

Hope it helps.

Wanwen

|||some more questions as well - what does the filtered column look like, and are you updating the filtered column?|||The filtered column is a bit field and is only updated at the server - with the partition options set to 3 (and use partition groups set to true) you cannot change that value at the subscriber. The field gets read only permissions in the database.|||The triggers I put in place to audit the updates to the table I am conerned with revealed that there were no updates occuring that were not expected.

So, what happens is the data gets inserted via a biztalk process. The data then gets synchronised to a mobile device where an update occurs.

Upon synchronisation, the data updates going back are met with a conflct - wwhich must surely be all but impossible if nothing has touched the data on the server.

To make matters worse, this doesn't occur for every updated record only for some of them. It also does not occur to other tables set up in the same way.

Something is very fishy about this..|||

Hi,

Could you please give more information so we can try to understand and repro the problem?

Could you return the contents of MSmerge_conflicts_info and MSmerge_conflict_publication_article table for the article where the conflict occurred? Also, there are probably some information about conflict in merge agent history. Do you have some primary key, foreign key constraint on publisher only? That will cause conflict if the subscriber row violated the constraint and failed to be applied on publisher.

Do you have join filters defined in your publication? when you do update, do you update the rows on both base article and join article? what is your subset_filter and join filter looks like?

Thanks

Wanwen

|||OK, more information as requested (should have done this when you asked the first time).

Two articles in my database that I am getting these unexplained
conflicts for.
job_travel
meter

CREATE TABLE [dbo].[job_travel](
[jot_id] [uniqueidentifier] NOT NULL CONSTRAINT [df_jot_id] DEFAULT (newid()),
[jot_guid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [df_jot_guid] DEFAULT (newsequentialid()),
[jot_job_id] [uniqueidentifier] NOT NULL,
[jot_travel_start] [datetime] NULL,
[jot_travel_stop] [datetime] NULL,
[jot_travel_duration] [int] NULL,
[jot_is_active] [bit] NOT NULL CONSTRAINT [df_jot_is_active] DEFAULT ((1)),
CONSTRAINT [pk_jot_id] PRIMARY KEY CLUSTERED
(
[jot_id] ASC
)WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF)
)

CREATE TABLE [dbo].[meter](
[met_id] [uniqueidentifier] NOT NULL CONSTRAINT [df_met_id] DEFAULT (newid()),
[met_guid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [df_met_guid] DEFAULT (newsequentialid()),
[met_job_id] [uniqueidentifier] NOT NULL,
[met_reading] [int] NULL,
[met_number] [varchar](20) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[met_is_active] [bit] NOT NULL CONSTRAINT [df_met_is_active] DEFAULT ((1)),
CONSTRAINT [pk_met_id] PRIMARY KEY CLUSTERED
(
[met_id] ASC
)WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF)
)

Each article hangs from the job table which in turn hangs from the sys_user table

joins to get there are as follows

-- Select the technician information
SELECT <published_columns> FROM [dbo].[sys_user] WHERE syu_code = SUSER_SNAME() AND syu_is_active = 1

-- select the jobs for the technician
SELECT <published_columns> FROM [dbo].[sys_user] INNER JOIN [dbo].[job] ON sys_user.syu_id = job.job_syu_id AND job.job_is_active = 1

-- select the job travel records for each job
SELECT <published_columns> FROM [dbo].[job] INNER JOIN [dbo].[job_travel] ON job.job_id = job_travel.jot_job_id AND job_travel.jot_is_active = 1

-- select the meter records for each job
SELECT <published_columns> FROM [dbo].[job] INNER JOIN [dbo].[meter] ON job.job_id = meter.met_job_id AND meter.met_is_active = 1

MSmerge conflict info for job_travel (3 useful columns - let me know if you need more)
conflict_type reason_code reason_text
2 2 The same column(s) of the same row was updated at both '25a - 1193b9285dee' and 'mas.canon_map'. The resolver chose the update from '25a - 1193b9285dee' as the winner.

A typical job_travel record from the conflict table

jot_id jot_guid jot_job_id jot_travel_start jot_travel_stop jot_travel_duration jot_is_active origin_datasource_id
5ED06CA2-C513-46EE-BA52-A7CD7327D195 A8243A8C-0316-DB11-807E-00145E2A163D 95BFBB97-694E-4526-8FBE-7D31CB35251C 2006-07-18 14:18:00.000 NULL NULL 1 1CEA745B-FAF4-4772-A5D1-3E644DD40874

MSmerge conflict info for meter (3 useful columns - let me know if you need more)

conflict_type reason_code reason_text
2 2 The same column(s) of the same row was updated at both '73w - e17b9ff3c3eb' and 'mas.canon_map'. The resolver chose the update from '73w - e17b9ff3c3eb' as the winner.

A typical meter record from the conflict table
met_id met_guid met_job_id met_reading met_number met_is_active origin_datasource_id
127380E3-E1AF-49BD-8B6C-FB5338287CDD F2D5A09B-0C15-DB11-807E-00145E2A163D 7594C31D-1805-46B8-B2A8-F1EDB46E8C06 NULL 1 1 1CEA745B-FAF4-4772-A5D1-3E644DD40874

<quote>
Also, there are probably some information about conflict in merge agent history
</quote>

Not sure what you're looking for here?

<quote>

Do you have some primary key, foreign key constraint on publisher only?

</quote>

No, constraints are consistent at both publisher and subscriber.

<quote>

Do

you have join filters defined in your publication?
</quote>

Yes, as shown above

<quote>

when you do update,

do you update the rows on both base article and join article?
</quote>

potentially.

Sometimes we will and sometimes we won't. Information on a meter or a job_travel record may change without any change to the job data. A meter or job_travel change does not force a change to the job record.

To re-iterate to data flow.

A record gets create at the publisher.
Synchronisation ensures the subscriber has access to the record.
A data update occurs at the subscriber. (job_travel.jot_travel_stop) (meter.met_reading)
NO data updates occur at the publisher.
Synchronsation ensures the change goes from the subscriber to the publisher.
On some occasions - not all - a conflict occurs.
The custom resolver (subscriber always wins) kicks in and resolves the data - EVENTUALLY. There is a definite delay in this process causing the data extract that has been triggered to extract unresolved data (publisher data before the update)

Hopefully this is sufficient information for you to continue with. Ask for more and I'll see what I can provide.

conflict Problem Help

Hello Everybody
I am having merge Replication using MSSQL 2000 sp3 latest security patch,
My replication is server1 Publisher, server2 subscriber, server3
subscriber,
Server4 subscriber, server5 subscriber. I am using schedule around 1:00
AM every day, In Server2 we insert 5 rows some value, and 5 rows sending to
Server3 using DTS with Insert statement, and server3 we update the 5Rows,
and sending to Server4 or server2, this all process everything done before
synchronize. I am using default conflict revolver, becoz some table dont
have date time field. When I run the merge agent, I got some conflict in
conflict tables. Automatically delete some row in subscriber.
How to resolve those problems. I need urgent help.
The same row was updated at 'THSWPSW002.GCP' and deleted at
'BKKNTS370.GCPTEST'.
The resolver chose the deletion as the winner.
3:3 conflict_type : reason_code
The same column(s) of the same row was updated at both 'SERVER1.APPTEST' and
' SERVER2.APPTEST '.
The resolver chose the update from ' SERVER1.APPTEST ' as the winner.
2:2
The row was inserted at ' SERVER5.APPTEST ' but could not be inserted at '
SERVER1.APPTEST '. Violation of PRIMARY KEY constraint
'PK__T_M_SUPPLIER__3607E224'. Cannot insert duplicate key in object
'T_M_SUPPLIER'.
5:2627
The row was inserted at 'SERVER1.APPTEST' but could not be inserted at
'SERVER2.APPTEST'. Violation of PRIMARY KEY constraint
'PK__T_M_SUPPLIER__38CF4036'. Cannot insert duplicate key in object
'T_M_SUPPLIER'.
6:2627
The same row was updated at both 'SERVER1.APPTEST' and 'SERVER5.APPTEST'.
The resolver chose the update from 'BKKNTS370.GCPTEST' as the winner.
1:1
Thanks
Sam
Sam,
please take a look at this article and see if it applies:
http://support.microsoft.com/default...&Product=sql2k
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks,
Still i have problem some conflict.
i change mergearticle error 'flase'
could you tell me how to handule ?
Sam
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ui2754ILGHA.2276@.TK2MSFTNGP15.phx.gbl...
> Sam,
> please take a look at this article and see if it applies:
> http://support.microsoft.com/default...&Product=sql2k
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>

Configuring new Subscriber. Publisher can't connect to Subscriber

Hi,
Both the publisher and subscriber are SQL 2005 SP2. I am trying to set up a
new subscriber to a push replication. I have other subscribers that are
working fine. When I try to add a new subscriber I am specifying the
computers name as the 'Server Name'. When the wizzard attempts to connect I
receive an error specifying that 'Cannot connect to XXXXX'. 'Timout expired.
The timeout period elapsed prior to completion of hte operation or the
server is not responding. (Microsoft SQL Server). Is these something that I
need configured on the subscriber machine? I'm sure I am missing something
obvious.
Thanks for your help,
Terry
its hard to say what is the problem here. Set the login timeout to something
large, perhaps 300. Enable logging to see if you can see where it is getting
stuck.
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
"Terry Wahl" <TerryWahl@.discussions.microsoft.com> wrote in message
news:78D0CB4F-5EFA-4D15-B13B-8F54F8D1BF2C@.microsoft.com...
> Hi,
> Both the publisher and subscriber are SQL 2005 SP2. I am trying to set up
> a
> new subscriber to a push replication. I have other subscribers that are
> working fine. When I try to add a new subscriber I am specifying the
> computers name as the 'Server Name'. When the wizzard attempts to connect
> I
> receive an error specifying that 'Cannot connect to XXXXX'. 'Timout
> expired.
> The timeout period elapsed prior to completion of hte operation or the
> server is not responding. (Microsoft SQL Server). Is these something
> that I
> need configured on the subscriber machine? I'm sure I am missing
> something
> obvious.
> Thanks for your help,
> Terry
|||Hi Hilary,
Thanks for the reply. It turns out that the firewall was the issue. Here
is the document that I used to configure the firewall:
http://msdn2.microsoft.com/en-us/library/ms175043(SQL.90).aspx
Thanks again,
Terry
"Hilary Cotter" wrote:

> its hard to say what is the problem here. Set the login timeout to something
> large, perhaps 300. Enable logging to see if you can see where it is getting
> stuck.
> --
> 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
> "Terry Wahl" <TerryWahl@.discussions.microsoft.com> wrote in message
> news:78D0CB4F-5EFA-4D15-B13B-8F54F8D1BF2C@.microsoft.com...
>
>