Re: Implementation of Replication en SQL SERVER 2K

From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 09/24/04 

Date: Fri, 24 Sep 2004 11:48:54 -0400

Great, glad you have a working solution. 

-- 
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Alvaro Rebolledo" <Alvaro Rebolledo@discussions.microsoft.com> wrote in
message news:E85FFC65-4500-46D7-930D-81E95B585414@microsoft.com...
> Thanks for the answer. In summary if I can do merge Replication, single
that
> the instantaneous changes nonserious. To my it serves asi to me, because I
> think to make the replications at the end of every day. And thanks for the
> data of the community in Spanish.
>
> "Hilary Cotter" wrote:
>
> > Hola Alvaro!
> >
> > Your English is better than my Spanish!
> >
> > Yes you can use merge to keep all the databases synchronized, but not
> > instantaneously. The lowest latency of merge can be a few seconds, but
you
> > will find for large throughput systems it may climb to several minutes.
> >
> > From what you describe it sounds like each branch, or SQL Server cannot
> > connect to each other. Network connectivity will be essential. You
mention
> > that you can use FTP. FTP can be used to pull the snapshot to the
respective
> > branch offices so the schema, data and the metadata which is used by
merge
> > replication can be distributed to the merge subscribers.  However the
SQL
> > Server Agents (servants as you call them) will need to be able to
connect
> > with each other. You will have to open up port 1433 on your firewalls.
> >
> > I hope that I have correctly guessed what you are asking.  Are you aware
> > that there is a spanish language newsgroup dedicated to SQL Server?
> >
> > Try microsoft.public.es.sqlserver
> >
> >
> > HTH
> >
> > -- 
> > Hilary Cotter
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> >
> > "Alvaro_rebolledo" <Alvaro_rebolledo@discussions.microsoft.com> wrote in
> > message news:664B382B-BCEE-41B0-9122-41EFF327BB39@microsoft.com...
> > > Hello, they excuse by ingles. I hope can understand to me. I have
several
> > BD
> > > SQLSERVER 2000, which all are of the same structure. But one in each
city,
> > > the objective is to know if I can use the option of Merge to maintain
all
> > the
> > > data bases synchronous. Exists algun problem if the servants where
estan
> > the
> > > data bases cannot be seen between? The unico which they tendrian in
common
> > is
> > > a site FTP where they podrian to let the archives to handle. Or in
which
> > it
> > > forms it must make the implementation so that the synchronization
works? I
> > > hope can help me, thanks
> >
> >
> >

Relevant Pages

  • Re: Single point of failure
    ... RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. ... Looking for a SQL Server replication book? ... "Hilary Cotter" wrote: ...
    (microsoft.public.sqlserver.replication)
  • Re: Single point of failure
    ... "Hilary Cotter" wrote: ... Looking for a SQL Server replication book? ... publisher and subscriber to each other and to the other publishers ...
    (microsoft.public.sqlserver.replication)
  • Re: Article Defaults --> cant change
    ... >> Hilary Cotter ... >> Looking for a SQL Server replication book? ... >>> We don't want data deleted on the subscribers when data is deleted on ...
    (microsoft.public.sqlserver.replication)
  • Re: UPDATE Statements May be Replicated as DELETE/INSERT Pairs
    ... Hilary Cotter ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge Replication is Broken
    ... Hilary Cotter ... Looking for a SQL Server replication book? ... > tablenick the name of that table or is it something else? ...
    (microsoft.public.sqlserver.replication)
Loading