Subscription database not being updated.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

klineb - 25 Feb 2006 07:09 GMT

Good Day.

I have a server running SQL Server 2000 SP4 as the Distributor and
Pulisher. I have multiple XP systems with MSDE SP4 installed as the
subscriber. The Databases on the XP systems have a database created
during installtion with all of the tables created.

I am running into a problem because the subscriber already has the
tables. But I need Identity range management to occur automatically.
(Identity range managment has been configured on the sever.)

Do I need to not install a complete database on the subscriber?

Thanks in Advance.

Brian

Reply to this Message

Paul Ibison - 27 Feb 2006 09:06 GMT

Brian,
if you want automatic identity range management then you'll need to
initialize the subscriber. For a nosync initialization, you'll have to
manage the ranges yourself.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Reply to this Message

klineb - 27 Feb 2006 14:41 GMT

Paul,

Can you initialize the subscriber at the time of creating the
subscription?

The subscription is created the first time the end user tries to sync
with the server.

Brian

Reply to this Message

Paul Ibison - 27 Feb 2006 14:48 GMT

Brian,
initialization is the normal process at the creation of the subscription. If
you're replicating to a database which already has the PKs and FKs there,
there can be issues - is that what you have seen? In this case you might
want to use a pre-snapshot script to drop the FKs or to use a completely new
database if at all possible.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Reply to this Message

klineb - 27 Feb 2006 19:36 GMT

Thanks for the reply.

Yes that is what I have seen.

Right now I have two installation options. The first option creates a
complete database with all tables, relations, PK, and FK's
The second option creates a database with only the non-replicated
tables.

I will try what you suggest.

Reply to this Message