Replication with MSDE

[Craig HB]

I have a distributed inventory control database that I am going to
migrate from Access to SQL Server. I am going to use SQL Server
Replication to keep the data current.

There will one SQL Server 2000 database at HeadOffice, and about 200
branches will each have MSDE 2000.

For tables that are the same for each branch (e.g. StockItems,
Suppliers), I'm going to use Transactional replication with the
HeadOffice as Publisher. There is no need for Merge replication,
because only HeadOffice will be changing this data.

For tables that are updated at the branches (e.g. deliveries, sales),
there shouldn't be any
conflicts either, as each branch will only update data that is
specific to it. So, transactional
replication with the Branches as Publishers seems like the answer.
BUT, MSDE 2000 only handles merge replication as a publisher, so it
looks like I'm going to have to use Merge Replication if I'm am going
to use MSDE.

Question: Do you think that it worth buying a full SQL Server licenses
for each branch, so that I can use Transactional replication with the
branches as publishers. Or, should I stick with MSDE 2000 and Merge
replication. Also, are there any other reasons why MSDE won't be
adequate as the database at the branches.

Thanks,
Craig

[Simon Hayes]

You seem to have two main questions - is it worth spending the money to be
able to implement transactional replication instead of merge; and is MSDE
generally suitable for your situation.

For the first question, I would consider asking it in
microsoft.public.sqlserver.replication - replication is a large topic, and
you may well get better advice in a specialized group (which isn't to say
that no one here knows anything about it, just that I don't know that much
about it myself, and so I would ask in a dedicated forum).

For the second point, I suggest you review the MSDE product information
here:

http://www.microsoft.com/sql/msde/pr...o/features.asp

The main limitations that might affect you are that you are limited to 2GB
databases, and performance drops quickly when you have more than 5
connections.

Simon

"Craig HB" <cr*****@bigfoot.com> wrote in message
news:3b**************************@posting.google.c om...

I have a distributed inventory control database that I am going to
migrate from Access to SQL Server. I am going to use SQL Server
Replication to keep the data current.

There will one SQL Server 2000 database at HeadOffice, and about 200
branches will each have MSDE 2000.

For tables that are the same for each branch (e.g. StockItems,
Suppliers), I'm going to use Transactional replication with the
HeadOffice as Publisher. There is no need for Merge replication,
because only HeadOffice will be changing this data.

For tables that are updated at the branches (e.g. deliveries, sales),
there shouldn't be any
conflicts either, as each branch will only update data that is
specific to it. So, transactional
replication with the Branches as Publishers seems like the answer.
BUT, MSDE 2000 only handles merge replication as a publisher, so it
looks like I'm going to have to use Merge Replication if I'm am going
to use MSDE.

Question: Do you think that it worth buying a full SQL Server licenses
for each branch, so that I can use Transactional replication with the
branches as publishers. Or, should I stick with MSDE 2000 and Merge
replication. Also, are there any other reasons why MSDE won't be
adequate as the database at the branches.

Thanks,
Craig