Consolidate multiple databases via merge replication

Hi
I am trying to merge a set of tables from 5 separate databases (4 on
separate servers and 2 on the same server) into one 'master' database.
The tables being replicated all have unique ID ranges
How to I organise the replication so that the subscriber database can allow
inserts which fit into the ID ranges for the related Publishers database.
ie All inserts with a Lab_ID = 'L' should ONLY be replicated back to the
associated publisher.
I am not familiar with the automatic identity range handling .. can anyone
point me to an article about how this works ?
any help would be appreciated
cheers
mike
Mike,
as you've got multiple publishers, just ordinary filters will work to
restrict the flow of data to each publisher. For identity range handling,
you'll need to design each publisher's range yourself. The subscriber table
can be created during the first initialization, and all others are nosync
ones. So, the subscriber's identity range is defined after the first
initialization, and subsequent publications need to be sure not to overlap
with this range. Make the ranges large, because assignment of another range
might cause an overlap, so if the range is so big there will never be any
need to reset then this is best.
Alternatively, all subscriptions can be nosync ones.
These might help:
http://www.replicationanswers.com/No...alizations.asp
http://www.replicationanswers.com/ManualIdentities.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Consequences of changing subscription expiry date SQL Server 2000

Hi,
I'm running a merge publication on a SQL Server 2000 database with
several anonymous subscribers. I want to change the subscription
expiry from 14 to 28 days. Aside from larger logging tables, are
there any important consequences to doing this? In particular, do I
need to reinitialise the subscriptions before the change takes effect?
Many thanks
Alex
There will be slower syncs. Yes you need to reinitialize.
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
<WombatDeath@.gmail.com> wrote in message
news:1173701986.327352.14330@.h3g2000cwc.googlegrou ps.com...
> Hi,
> I'm running a merge publication on a SQL Server 2000 database with
> several anonymous subscribers. I want to change the subscription
> expiry from 14 to 28 days. Aside from larger logging tables, are
> there any important consequences to doing this? In particular, do I
> need to reinitialise the subscriptions before the change takes effect?
> Many thanks
> Alex
>
|||Thanks Hilary. If I don't reinitialize the existing subscriptions
will they break, or will they just keep the old 14-day expiration time
until I get around to reinitializing them for other reasons?
Thanks
Alex

Connection Problem with the Workstation

Hi all;

I am trying to replicate our database by using the merge replication.
>From server side I tried to connect to the workstation. I have
installed MSDE to the client machine. I can see the machine name on the
SQL Server Group however I wasnt able to create the conncetion between
the machines. I have checked my network connection, there is no problem
I can see the machine and I can connect it through the network. I tried
to use Client Network Utility with Named Pipes and TCP/IP but not a
good news. I couldnt achieve to connect to the machine. So could
someone please help me out with this problem. I am really in trouble I
have to find out this end of this week.

Regards
As"laststubborn" <arafatsalih@.gmail.com> wrote in message
news:1104862206.970118.48710@.c13g2000cwb.googlegro ups.com...
> Hi all;
> I am trying to replicate our database by using the merge replication.
>>From server side I tried to connect to the workstation. I have
> installed MSDE to the client machine. I can see the machine name on the
> SQL Server Group however I wasnt able to create the conncetion between
> the machines. I have checked my network connection, there is no problem
> I can see the machine and I can connect it through the network. I tried
> to use Client Network Utility with Named Pipes and TCP/IP but not a
> good news. I couldnt achieve to connect to the machine. So could
> someone please help me out with this problem. I am really in trouble I
> have to find out this end of this week.
> Regards
> As

You don't mention your version of MSDE, but network access is disabled in
MSDE 2000 SP3a:

http://support.microsoft.com/kb/814130

Simon|||yeah I have installed 2000 SP3a then should I install SQL2000 client
version to my workstation?|||"laststubborn" <arafatsalih@.gmail.com> wrote in message
news:1104873576.019320.324770@.z14g2000cwz.googlegr oups.com...
> yeah I have installed 2000 SP3a then should I install SQL2000 client
> version to my workstation?

If you have MSDE 2000 SP3a, then by default you cannot access it from the
network, so that is probably why you cannot connect to the MSDE installation
on your workstation from your server (if I understood your problem
correctly). As mentioned in the KB article, you can use the MSSQL network
utility to enable network support, and then you should be able to connect to
MSDE from other computers.

Simon