Trouble using identity ranges for subscribers of a merge replication 
Author Message
 Trouble using identity ranges for subscribers of a merge replication

After the initial snapshot with the "DROP and re-create" option,

I remove the subscriber from the subscribers-list to edit the subscribtion
tables to have its specific identity range.

Then, I put the subscriber back on the subscribers-list and change the
snapshot option to
"Delete data in the existing table that matches the row filter". I also
leave the
"Include declared referential integrity on the primary keys" SELECTED!

When I run the re-sync, everyting is fine except the subscriptions table now
miss all the FK-relations, which were there before.

It looks like, that the "Include referential integrity" option is silently
connected to the
"DROP the existing table and re-create it" option.

But when I would use this option, I would loose the identity range settings.

A real dilemma!

So, currently I have to manually re-create the lost FK-relations.

Question:
Am I doing smth. wrong, or is it just the way it has to be?

Many thanks in advance.

Erd?l Biramen MCP+Internet, MCSE, MCSD, MCDBA, MCT



Tue, 23 Apr 2002 03:00:00 GMT
 Trouble using identity ranges for subscribers of a merge replication

I do not resend the data.  I subscribe and get the initial synch.  Then
unsubscribe, add the identity with the seed and increment that I want, set
it as not for replication, resubscribe without sending schema or data.  I
then stop the merge agent and issue a replmerg with a -Validate 2 option to
get things into synch and turn the merge agent back on.

--

Mike
New product reviews: http://www.mssqlserver.com/products
Book reviews: http://www.mssqlserver.com/books
Replication Primer: http://www.mssqlserver.com/replication
Disaster recovery plans: http://www.mssqlserver.com/backup
SYSOP PASS Discussion Forums: http://www.sqlpass.org
Please post all replies to the newsgroup unless stated otherwise.



Fri, 26 Apr 2002 03:00:00 GMT
 Trouble using identity ranges for subscribers of a merge replication
Yes, resubscribing without sending schema or data is exactly what I need.

The problem is, that I still loose all of my FK-constraints, even when
choose "No, the subscriber has already the schema and data", while creating
the push subscription. I have to re-create them manually after
re-subscribing.

The other issue is, that the resubscribing takes well over an hour although
no schema or data is being sent. The publication has 6 tables with each one
having a couple of hundert rows.

Erd?l


Quote:
> I do not resend the data.  I subscribe and get the initial synch.  Then
> unsubscribe, add the identity with the seed and increment that I want, set
> it as not for replication, resubscribe without sending schema or data.  I
> then stop the merge agent and issue a replmerg with a -Validate 2 option
to
> get things into synch and turn the merge agent back on.

> --

> Mike
> New product reviews: http://www.mssqlserver.com/products
> Book reviews: http://www.mssqlserver.com/books
> Replication Primer: http://www.mssqlserver.com/replication
> Disaster recovery plans: http://www.mssqlserver.com/backup
> SYSOP PASS Discussion Forums: http://www.sqlpass.org
> Please post all replies to the newsgroup unless stated otherwise.



Sat, 27 Apr 2002 03:00:00 GMT
 Trouble using identity ranges for subscribers of a merge replication
When you reset your identity value on the subscribe side, you don't
need to unsubscribe anything. After the initial snapshot, you can just
use DBCC to reset your specific identity value. The syntax is:
DBCC CHECKIDENT (table_name, reseed, new_seed_value).

Hope this will save you some time.

Hank



Quote:
> After the initial snapshot with the "DROP and re-create" option,

> I remove the subscriber from the subscribers-list to edit the
subscribtion
> tables to have its specific identity range.

> Then, I put the subscriber back on the subscribers-list and change the
> snapshot option to
> "Delete data in the existing table that matches the row filter". I
also
> leave the
> "Include declared referential integrity on the primary keys" SELECTED!

> When I run the re-sync, everyting is fine except the subscriptions
table now
> miss all the FK-relations, which were there before.

> It looks like, that the "Include referential integrity" option is
silently
> connected to the
> "DROP the existing table and re-create it" option.

> But when I would use this option, I would loose the identity range
settings.

> A real dilemma!

> So, currently I have to manually re-create the lost FK-relations.

> Question:
> Am I doing smth. wrong, or is it just the way it has to be?

> Many thanks in advance.

> Erd?l Biramen MCP+Internet, MCSE, MCSD, MCDBA, MCT

Sent via Deja.com http://www.deja.com/
Before you buy.


Sun, 28 Apr 2002 03:00:00 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Merge replication with identity value ranges using not for replication option

2. Merge Replication and Identity Problems on Subscribers

3. merge replication conflict and identity range problem

4. Identity range adjustment in Merge Replication

5. 2 subscribers have the same identity range?

6. new identity range on subscriber barfing

7. Subscriber can't insert data in the table with identity range

8. Identity Range Management with Merge Repl

9. The merge process could not retrieve identity range resource for table

10. Identity Range Management with Merge Repl

11. Identity range is not being renewed during a merge

12. Merge Repl., Identity Ranges, SQL CE & CompactDatabase


 
Powered by phpBB® Forum Software