Thank you for the answer.
My customer have a MS Access 2000 replica set: hub replica in headquarters
and replicas in regional offices, indirect replication by dial-up or ASDL.
Now they want to upsize to SQL server 2000: SQL server 2000 in headquarters
and MSDE in regional offices (because of the cost). Headquarters gets all
records from regional offices, regional offices get from headquarters only
new records from lookup tables and they do not send data each other.
Rgds
[quoted text, click to view] "Paul Ibison" wrote:
> Please explain a bit more about your business
> requirements. MSDE is not usually used as a publisher,
> and in fact cant be used as a TR publisher. In many cases
> it is suitable to use it as a subscriber in merge
> replication, where anyway the publisher/subscriber
> metaphor doesn't really hold. This article will help give
> you more technical info:
>
http://support.microsoft.com/default.aspx?scid=kb;en- > us;Q324992
> Rgds,
> Paul Ibison SQL Server MVP,
www.replicationanswers.com > (recommended sql server 2000 replication book:
>
http://www.nwsu.com/0974973602p.html)
>
I would set up the headquarters as a publisher in merge
replication. Each subscriber uses MSDE and the
replication type is merge. The data is partitioned
according to subscriber using dynamic filters. Done this
way, you'll only need to set up one publication. If you
don't want to overhaed of dynamic filters, you could use
a separate publication for each subscriber.
I would recommend a separate publication for the lookup
tables involving transactional replication.
Rgds,
Rgds,
Paul Ibison SQL Server MVP,
www.replicationanswers.com (recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Normally no, however some software designers prefer to group data into
different databases according to functionality or recovery purposes. For
instance SQL Server stored most global stored proceeders, database file
information, and login information in the master database. The job
scheduling information is stored in the msdb database. Replication
information is stored in the distribution database.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html [quoted text, click to view] "Thang Long" <ThangLong@discussions.microsoft.com> wrote in message
news:A1D878A6-6E78-4D99-BB73-3253FA287456@microsoft.com...
> Verry Happy New Year
> Sorry for stupid question.
> Would I put lookup tables into a diferent database ?
> Thank you very much