Merge seems to hang at conflict and conflict is not logged

We have a SQL2005 merge replication database with 8 subscribers. Three of the
subscribers have not successfully replicated. We would appreciate any
additional ideas for correcting this. So far we have some inconsistencies.
For example, the "View Synchronization Status" displays:
"Downloaded 100 change(s) in 'OurTable' (100 updates, 1 conflict)"
and the publisher's "Microsoft Replication Conflict Viewer" displays:
"There are no conflicts to view."
If you have any ideas why conflicts are causing the replication to fail
while the conflict viewer shows no conflicts, we would appreciate your input.
Thanx.
Were there any conflicts on the subscriber side?
You can run the conflict viewer there as well, or if that's not
convenient/possible there are sp_xxx procedures to help you view the
conflict tables on the client...

Merge rplication - records not being replicated.

We are replicating 5 subscriptions to 500 users with MSDE databases. All
databases are SQL Server 2000 SP4.
The issue we are seeing is that some users are not seeing all the records
they should. (Merge replication) Examples:
User A creates some new records. The records get replicated to the server
and then are not in user A's database (they should still be in the users
database). There are no conflicts. Re-building the snap shot and
re-initializing with the upload changes selected does not fix the issue.
Re-building the snap shot and re-initializing with the upload changes Not
selected does fix the issue.
Any suggestions for tracking this proble down would be appreciated.
Are you using any dynamic filters? If the added rows on A are not allowed
according to the filter, the row is outside of the partition and this could
account for such behaviour.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
We are using dynamic filters. The users are only allowed to add records
that are in the partition.
|||Then this is normal behaviour.
It would help if you explain a little more about what you would like to
happen.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

merge replication with a emulator.

- A database in Sql Server2000 running in a PC with windows2000
- Replicated database in Sql Server CE running in a emulator of
PocketPC
In merge replication between both databases i want access to tables in PocketPc from SqlServer in PC. how can i do it?It is not possible access Pocket PC emulator DB from SQL Server.

Instead of that you can access to the emulator DB with the program
provided by SQL Server CE isqlw20.exe (You must use the correct
version to run it in emulator).

Good Luck!sql

Merge Replication updating SP3 to SP4

Gurus,
I am planning to update SP3 to SP4 on a replicated server.
A- Please correct me if i wrong in order.
1- Apply SP4 on Publisher / Distributor (on single box)
2- All subscribers.
B- As per my knowledge there are no issues while applying SP4. Is there any
known issue while applying the sp4 has to be taken care of?
TIA
Regards
Javed Iqbal
Javed,
I agree with the order. I've had a search of this newsgroup (using Google
Groups) to check for sp4 and there are hardly any reported errors so far.
The main on e is
http://groups.google.com/group/micro...85 a5a37097d4
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Merge Replication Schema Changes

We have three distinct environments that a databse resides in: a lab
environment, merge replicated with other lab servers, a production
environment, merge replicated with other production servers, and a
development environment not replicated anywhere. We do not want day-to-day
development (schema and data changes) to effect either the lab or production
environments, however periodically would like to take these changes and apply
them to the lab environment. Unfortunately, all tools that we have used to
copy these schema changes from development to lab fail since replication is
not configured in the development environment (and therefore schema migration
fails due to the lack of row guids and/or default value differences). How
can we easily and routinely (but manually) package schema changes from a
non-replicated database and push them into a replicated database, without
breaking replication itself? Once the schema is migrated, moving data seems
trivial.
It seems that your problem is due to the guids and related metadata not
being present in the dev environment. I think the best way to do this would
be to either merge publisher the dev environment, or to add the guid columns
with the unique indexes on each table you are replicating like this:
alter table MyTable
add [rowguid] [uniqueidentifier] ROWGUIDCOL
NOT NULL
CONSTRAINT [MSmerge_df_rowguid_MyTable] DEFAULT (newid())
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Zer0Day" <Zer0Day@.discussions.microsoft.com> wrote in message
news:2B2E7210-1416-482D-AC33-31DD7CEA1A67@.microsoft.com...
> We have three distinct environments that a databse resides in: a lab
> environment, merge replicated with other lab servers, a production
> environment, merge replicated with other production servers, and a
> development environment not replicated anywhere. We do not want
> day-to-day
> development (schema and data changes) to effect either the lab or
> production
> environments, however periodically would like to take these changes and
> apply
> them to the lab environment. Unfortunately, all tools that we have used
> to
> copy these schema changes from development to lab fail since replication
> is
> not configured in the development environment (and therefore schema
> migration
> fails due to the lack of row guids and/or default value differences). How
> can we easily and routinely (but manually) package schema changes from a
> non-replicated database and push them into a replicated database, without
> breaking replication itself? Once the schema is migrated, moving data
> seems
> trivial.

Merge Replication Schema Change

Using merge replication do schema changes made to the publisher automatically get replicated to the subscriber or is it necessary to reinitialize the subscription.
Thanks,
Lance
Replication Newbie
Assuming you're using sp_repladdcolumn, sp_repldropcolumn then it is
automatic.
HTH,
Paul Ibison
|||Thanks, What about new tables, indexes, and constraints?
|||Lance,
for new tables, you can use sp_addmergearticle. When you add the article,
you can choose whether to take indexes, constraints using @.schema_option.
HTH,
Paul Ibison
sql

Merge replication of Foreign keys

Hi.
I need to add a new foreign key to a merge replicated table (It references
the PK in the same table). Is there anyway of replicating this to the other
subscribers without invalidating the snapshot or applying it separately on
each server?
AFAIK - no!
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"robham" <nospam@.co.uk> wrote in message
news:uXAUdaeiEHA.704@.TK2MSFTNGP12.phx.gbl...
> Hi.
> I need to add a new foreign key to a merge replicated table (It references
> the PK in the same table). Is there anyway of replicating this to the
other
> subscribers without invalidating the snapshot or applying it separately on
> each server?
>
|||Robham,
is the FK to be just a constraint? If so then I don't think it is possible
directly. I suppose you could use a combination of sp_repladdcolumn and
sp_repldropcolumn to achieve your aim but in some cases it is easier to
restart and do a noinit initialization.
If it is a new column, then sp_repladdcolumn should do it.
HTH,
Paul Ibison

Merge replication join filter clause can be subquery, self join?

Hi,
I need to filter the replicated rows of a table by using a subquery that
references to itself, or by doing a self join. My filter for the table
called "aCrediAnti" looks like:
Select *
From aCrediAnti t1
Where t1.ImpSaldoAntiMonOri > 0
Or exists(select * from aCrediAnti t2
Where t2.ClaOperProvCrediAnti = t1.ClaOperCrediProv
And t2.FolOperProvCrediAnti = t1.FolOperCrediProv
And t2.ClaEmp = t1.ClaEmp
And t2.ImpSaldoAntiMonOri > 0
)
Or may be also in the self join syntax
Select *
From aCrediAnti t1
Left Join aCrediAnti t2
On t2.ClaOperProvCrediAnti = t1.ClaOperCrediProv
And t2.FolOperProvCrediAnti = t1.FolOperCrediProv
And t2.ClaEmp = t1.ClaEmp
Where t1.ImpSaldoAntiMonOri > 0
Or (
Not t2.FolOperProvCrediAnti Is Null
And t2.ImpSaldoAntiMonOri > 0
)
My problem is how to specify such a filter. For both I need to specify table
aliases (t1, t2) for using them on the join, but neither the Enterprise
Manager and sp_addmergefilter (script version) allows me to use alias. What
can I do?
Thanks in advance
Faustino Dina
If my email address starts with two 'f'
drop the first 'f' when mailing me.
I think a UDF would be ideal for something like this.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"faustino Dina" <ffdina@.matusa.com.mx> wrote in message
news:O91w%238DkEHA.3664@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I need to filter the replicated rows of a table by using a subquery that
> references to itself, or by doing a self join. My filter for the table
> called "aCrediAnti" looks like:
> Select *
> From aCrediAnti t1
> Where t1.ImpSaldoAntiMonOri > 0
> Or exists(select * from aCrediAnti t2
> Where t2.ClaOperProvCrediAnti = t1.ClaOperCrediProv
> And t2.FolOperProvCrediAnti = t1.FolOperCrediProv
> And t2.ClaEmp = t1.ClaEmp
> And t2.ImpSaldoAntiMonOri > 0
> )
> Or may be also in the self join syntax
> Select *
> From aCrediAnti t1
> Left Join aCrediAnti t2
> On t2.ClaOperProvCrediAnti = t1.ClaOperCrediProv
> And t2.FolOperProvCrediAnti = t1.FolOperCrediProv
> And t2.ClaEmp = t1.ClaEmp
> Where t1.ImpSaldoAntiMonOri > 0
> Or (
> Not t2.FolOperProvCrediAnti Is Null
> And t2.ImpSaldoAntiMonOri > 0
> )
> My problem is how to specify such a filter. For both I need to specify
table
> aliases (t1, t2) for using them on the join, but neither the Enterprise
> Manager and sp_addmergefilter (script version) allows me to use alias.
What
> can I do?
> Thanks in advance
> --
> Faustino Dina
> If my email address starts with two 'f'
> drop the first 'f' when mailing me.
>
|||> I think a UDF would be ideal for something like this.
Thanks! Despite it took me hours to decode what "UDF" means ;-) it looks it
works
Faustino

Merge Replication Issue

Hello, I have a merge replication problem. I have one publisher/distributor
and roughly about 40 subcribers to a replicated database of about 10 gig
in size. I'm using SQL 2000 and have Sql sp3 on all my machines. I
wanted to do some maintenance on my publsher and so I changed in the
subscriber's job schedule the "Start Date" to be the next day. I don't know
why but this caused the replications between the subscribers and the
publishers to fail. The error message I received stated the following,
"The process could not check the existence of the generation at the 'Publisher'".
This message would appear after a 10 minute delay. So, I decided to
change the "Start Date" back to the original date and just synch one of
my subscriber. It started synching alright, but it seems to be going
through several generations. It has taken the subscriber over six hours
to synch and it has it not finished. I need to know if this is normal
and how can I shorten the process. I thought it would just synch back
with the publishers and upload the 1-day changes and not go through all
the generations.

Thanking you in advance for any assistance with this issueYou probably need to check this and see what settings need to be affected when attempting to suspend merge agents:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replmon_9pwh.asp|||First thank you for the reply. The article explained the problem I was going through.

We fortunately found the root of our problem. It was not so much the validations that were happening at the subscriber but an individual subscriber that had a extremely large msgenhistory table that it wanted to compare with the distributor. This particular subscriber was a new subscriber and should not had needed to be trying to validate it's data since it had just received a new snapshot. So, we dumped it's gehist and that helped. After this we started to first start to synch our subscribers and as soon as they started validating the articles, we stopped the synchronization procees. We then immediately started the synch process again and everything was fine. We had to do this for every one of the 40 subscribers.

Hope our experience helps others.

merge replication disable

I took a backup from a merge replicated database and restored it to a
non-replicated db. I want to make changes to the db but the system still
thinks the db is replicated, and I can't seem to get rid of any articles or
publications.
How can I undo the various replication flags and whatever?
try this
http://www.tech-archive.net/Archive/...4-03/0886.html
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul J." <Paul J.@.discussions.microsoft.com> wrote in message
news:996FA174-5039-4BCE-99E2-CDF52B8368B1@.microsoft.com...
> I took a backup from a merge replicated database and restored it to a
> non-replicated db. I want to make changes to the db but the system still
> thinks the db is replicated, and I can't seem to get rid of any articles
or
> publications.
> How can I undo the various replication flags and whatever?

Merge replication and FK

Hi ,
I have an stronge problem with my merge replication.
When i make change in publisher , is replicated immediatly to subscriber but
when i make change in subscriber , is not replicated to publisher and the
changes in subscriber is rollback.
i think the problem is in the FK's or the priority between publisher and
subscriber.
please help.
chouaib
Please see my reply to your other (identical ) post.
Rgds,
Paul Ibison (SQL Server MVP)
[vbcol=seagreen]

Merge Replication + Structure Changes

My company maintains 40 replicated Sybase databases using a merge
replication approach. It's difficult to update all 40 databases when a
structure change occurs. Structure changes are minor, usually adding
fields.

We are considering moving to SQL Server 2000 in the hope that these
updates will be easier to do. Does SQL Server 2000 support structure
updates accross replicated databases?

Martin"Martin McNally" <mcnally_martin@.hotmail.com> wrote in message
news:3cf569e1.0405031052.574c19e9@.posting.google.c om...
> My company maintains 40 replicated Sybase databases using a merge
> replication approach. It's difficult to update all 40 databases when a
> structure change occurs. Structure changes are minor, usually adding
> fields.
> We are considering moving to SQL Server 2000 in the hope that these
> updates will be easier to do. Does SQL Server 2000 support structure
> updates accross replicated databases?
> Martin

MSSQL supports adding or dropping columns while using any type of
replication. You might want to post this in
microsoft.public.sqlserver.replication, as people there may be able to give
more detail about any common issues or disadvantages.

Simon|||mcnally_martin@.hotmail.com (Martin McNally) wrote in message news:<3cf569e1.0405031052.574c19e9@.posting.google.com>...
> My company maintains 40 replicated Sybase databases using a merge
> replication approach. It's difficult to update all 40 databases when a
> structure change occurs. Structure changes are minor, usually adding
> fields.
> We are considering moving to SQL Server 2000 in the hope that these
> updates will be easier to do. Does SQL Server 2000 support structure
> updates accross replicated databases?
> Martin

hello martin!!

Try dbMaestro. It's a product that allows comparison, migration and
archiving of database schema and data in Sql Server 2000. by migration
you can updates structures of databases and data.

You can find it here:

http://www.extreme.co.il