all groups > sql server replication > february 2006 >
You're in the

sql server replication

group:

Subscription database not being updated.


Subscription database not being updated. klineb
2/24/2006 11:09:41 PM
sql server replication:
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
Re: Subscription database not being updated. Paul Ibison
2/27/2006 12:00:00 AM
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)

Re: Subscription database not being updated. klineb
2/27/2006 6:41:26 AM
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
Re: Subscription database not being updated. klineb
2/27/2006 11:36:04 AM
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.
Re: Subscription database not being updated. Paul Ibison
2/27/2006 2:48:53 PM
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)

AddThis Social Bookmark Button