Replication - Snapshots

Hi there,
I am looking at setting up a solution that relies on replication of data to
many publications. I believe what I need is merge replication. In this
scenario, many companies will receive data from the master publication but
each company should ONLY receive information for their concern. How do I get
the replication of these 250 companies to "configurably" only receive the
data they need.
Thanks in advance
what you are describing is a filtered publication.
You have two options create a publication which filters rows based on some
hardcoded value, is SalesID=123213, or using a dynamic filter where the
publication detects some property about the subscriber and only sends rows
to that subscriber, ie hostname() or @.@.servername. Dynamic filters work best
with pull subscriptions.
The technology is called horizontal partitioning, as you are creating your
publication you will get to a dialog called Customize the Properties of the
Publication. Select Yes, and then select Horizontally, by filtering the rows
of published data. Enter a filter clause that will filter the rows so that
only the rows you want to end up on the subscriber land there.
It also sounds like what you need is transactional replication
"Murray Foxcroft" <murray.foxcroft@.ast.co.za> wrote in message
news:OplWrAzFEHA.2980@.TK2MSFTNGP09.phx.gbl...
> Hi there,
> I am looking at setting up a solution that relies on replication of data
to
> many publications. I believe what I need is merge replication. In this
> scenario, many companies will receive data from the master publication but
> each company should ONLY receive information for their concern. How do I
get
> the replication of these 250 companies to "configurably" only receive the
> data they need.
> Thanks in advance
>

Replication

when using snapshots in replication, these files get copied to the hard drive. Can they be automatically deleted after the snapshot is posted?
Thanks
Niles,
if you have anonymous subscribers then they'll stay around until the publication's subscriber's timeout value. If you have standard subscribers, these files will be removed once they have all initialized. For transactional, this is when the distribution a
gent of each subscriber has run. The agent which removes the snapshot files is the distribution cleanup agent, which runs every 10 mins. You could run this immediately (manually) after your last initialization or you could schedule it to run more frequent
ly.
HTH,
Paul Ibison
|||What is the difference between anonymous subscriptions and standard and can it be switched easily
Thanks
|||An anonymous subscription is a type of pull subscription for which detailed
information about the subscription and the Subscriber is not stored. The
Subscriber is responsible for keeping an anonymous subscription
synchronized, and they are particularly used if Subscribers use the Internet
to access publications.
sp_helpsubscription will tell you if the subscription is anonymous or
http://msdn.microsoft.com/library/de...repl3_4dym.asp
Typically, the Subscriber is not explicitly named at the Publisher when
using anonymous subscriptions. So to change from a named subscription to an
anonymous one is not so simple and you'd drop and recreate the subscription.
To see if any of this is relevant to your case have a look at the
allow_anonymous value of sp_helppublication.
HTH,
Paul Ibison

Replication

when using snapshots in replication, these files get copied to the hard drive. Can they be automatically deleted after the snapshot is posted
ThanksAn anonymous subscription is a type of pull subscription for which detailed
information about the subscription and the Subscriber is not stored. The
Subscriber is responsible for keeping an anonymous subscription
synchronized, and they are particularly used if Subscribers use the Internet
to access publications.
sp_helpsubscription will tell you if the subscription is anonymous or
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_repl3_4dym.asp
Typically, the Subscriber is not explicitly named at the Publisher when
using anonymous subscriptions. So to change from a named subscription to an
anonymous one is not so simple and you'd drop and recreate the subscription.
To see if any of this is relevant to your case have a look at the
allow_anonymous value of sp_helppublication.
HTH,
Paul Ibison

Replication

when using snapshots in replication, these files get copied to the hard driv
e. Can they be automatically deleted after the snapshot is posted?
ThanksNiles,
if you have anonymous subscribers then they'll stay around until the publica
tion's subscriber's timeout value. If you have standard subscribers, these f
iles will be removed once they have all initialized. For transactional, this
is when the distribution a
gent of each subscriber has run. The agent which removes the snapshot files
is the distribution cleanup agent, which runs every 10 mins. You could run t
his immediately (manually) after your last initialization or you could sched
ule it to run more frequent
ly.
HTH,
Paul Ibison|||What is the difference between anonymous subscriptions and standard and can
it be switched easily
Thanks|||An anonymous subscription is a type of pull subscription for which detailed
information about the subscription and the Subscriber is not stored. The
Subscriber is responsible for keeping an anonymous subscription
synchronized, and they are particularly used if Subscribers use the Internet
to access publications.
sp_helpsubscription will tell you if the subscription is anonymous or
l3_4dym.asp" target="_blank">http://msdn.microsoft.com/library/d.../>
l3_4dym.asp
Typically, the Subscriber is not explicitly named at the Publisher when
using anonymous subscriptions. So to change from a named subscription to an
anonymous one is not so simple and you'd drop and recreate the subscription.
To see if any of this is relevant to your case have a look at the
allow_anonymous value of sp_helppublication.
HTH,
Paul Ibison