How To set up Replication for this really daring (poor) Architecture?

Hi,
I'm totally new to Replication. I'm reading the whole mornign alreaddy docs
and pages about it, but I still don't know how to solve this situation:
My (new) company has different Production-Sites, and one Main Office. All of
them have a copy of an Sql Server 2000 Database. One or two times a week, a
Raplication should happen:
- for some tables: From the Production-Sites to the Main Office
- for other tables: From the Main Office to the Production-Sites
It goed about 400-500 records a week for every site, mainly Inserts, but
from time to time also Updates an Deletes.
And now comes the tricky part: They don't have a connection between them!
They are in a country in which Internet isn't yet invented, hehe. The
communication happens with some type of Radio, with very poor quality, very
slow etc.
So what I need is: one or two times a week (they have to do the whole
Replication stuff manually) a file with the changes, that can be send to the
other site. After that a confirmation should be send back (which can take
easily some days).
I'm not asking for a whole solution, but things that can help me, that can
put me on the way. Like some step for step wizard that will help me
configure everything for this situation. Only two things are imported: the
replication should work 100% correct, and the size of the files that has to
be send, must be as low as possible!
I guess I should be using Queued transactional Replication? But for the
rest...
Any help would be really appreciated! Thanks a lot in advance.
Pieter
disable your distribution clean up agent. Run a job that runs once a
day which will pipe sp_browsereplcmds to a new table - like this
declare @.datetable varchar(25)
set @.datetable='['+convert(varchar(20),getdate())+']'
exec sp_browsereplcmds @.results_table=@.datetable
then run the distribution clean up job
You will get a table which contains all the commands you need to sync
the two databases. Run this on the branch offices. Do the same thing in
the brancj offices and run this in the central office.
With luck you will have no conflicts, otherwise you will have to figure
out how best to handle the conflicts.
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
DraguVaso wrote:
> Hi,
> I'm totally new to Replication. I'm reading the whole mornign
alreaddy docs
> and pages about it, but I still don't know how to solve this
situation:
> My (new) company has different Production-Sites, and one Main Office.
All of
> them have a copy of an Sql Server 2000 Database. One or two times a
week, a
> Raplication should happen:
> - for some tables: From the Production-Sites to the Main Office
> - for other tables: From the Main Office to the Production-Sites
> It goed about 400-500 records a week for every site, mainly Inserts,
but
> from time to time also Updates an Deletes.
> And now comes the tricky part: They don't have a connection between
them!
> They are in a country in which Internet isn't yet invented, hehe. The
> communication happens with some type of Radio, with very poor
quality, very
> slow etc.
> So what I need is: one or two times a week (they have to do the whole
> Replication stuff manually) a file with the changes, that can be send
to the
> other site. After that a confirmation should be send back (which can
take
> easily some days).
> I'm not asking for a whole solution, but things that can help me,
that can
> put me on the way. Like some step for step wizard that will help me
> configure everything for this situation. Only two things are
imported: the
> replication should work 100% correct, and the size of the files that
has to
> be send, must be as low as possible!
> I guess I should be using Queued transactional Replication? But for
the
> rest...
> Any help would be really appreciated! Thanks a lot in advance.
> Pieter
|||Err I'm sorry but i don't understand a Word of it...
How should I configure the SQL Server that has the changed tables? As a
Distributor, or a Subscriber, or a Publisher, or both of them?
And what has to be in the configuration of it? And Should I use the
Transactional Replication?
I'm new to Replication, so thank you very much for your help, but I don't
knwo where to put it and to do what exactly.
Until now I hasn't been able to do any replciation yet :-(
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:1114166996.038504.145260@.l41g2000cwc.googlegr oups.com...
> disable your distribution clean up agent. Run a job that runs once a
> day which will pipe sp_browsereplcmds to a new table - like this
> declare @.datetable varchar(25)
> set @.datetable='['+convert(varchar(20),getdate())+']'
> exec sp_browsereplcmds @.results_table=@.datetable
> then run the distribution clean up job
> You will get a table which contains all the commands you need to sync
> the two databases. Run this on the branch offices. Do the same thing in
> the brancj offices and run this in the central office.
> With luck you will have no conflicts, otherwise you will have to figure
> out how best to handle the conflicts.
> --
> 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
>
> DraguVaso wrote:
> alreaddy docs
> situation:
> All of
> week, a
> but
> them!
> quality, very
> to the
> take
> that can
> imported: the
> has to
> the
>