> Hola!
>
> In English this is termed transactional or snapshot
> replication with immediately updating subscribers.
>
> 1) there are no real hardware requirements, but you must
> have MS DTC running on both servers. You MUST have a very
> well connected connection otherwise updates at the
> subscribers will fail after hanging for 20 or more
> seconds. You will get a server access denied error
> message.
>
> 2) yes
>
> 3) Performance will be degraded slightly more than pure
> transactional replication but less than merge replication.
>
> The real problem with immediately updating subscribers is
> that all transactions will be applied on the publihsher as
> singletons which mean one row at a time.
>
> So if you have subscribers where a lot of data is been
> updated you might find your performance and latency to be
> worse than with pure transactional.
> >-----Original Message-----
> >Hello,
> >
> >I am just started in this, but I am interested in what in
> spanish is called
> >"duplicacion de instantaneas", I dont know the proper
> trasnlation to english
> >so I will try t explain it. This allows to sincronized a
> pasive database on
> >the server with the active database on the client who is
> running the
> >application trough TCP/IP and there are some things I
> want to know
> >1) What are the server requirements to do this (ram,
> bandwidth. etc) to be
> >able to check the client data in the server in real time.
> >2) Is this schema possible if the server is running sql
> server 200 and the
> >client MSDE? If so, which are mi limitations?
> >3) Is the client performance damage with the
> sincronization? If so, are somo
> >percentages of this?
> >
> >Thanks
> >
> >Brenda
> >
> >
> >
> >
> >
> >.
> >