Replication on 130GB db

Is there anyone with some expirience in replicating such large database?
Maybe some good link or something like that. I would need trans replication
instructions.
regards,
DaliborIf you have a fast link between your publisher/distributor/subscriber,
replicating 130GB is still managble, especially when the amount of data
changes is relatively small in comparison with the total database size. We
are replicating bigger database than that with transactional replication.
With 130GB of data, it could be a major headache to re-snapshot your
publication, which may take a while in most environments. It can become a
major problem when you don't have a large maintenance window. For us, the
most common reason for requiring a new snapshot is new releases of the
application that introduce database schema changes. Once we have reined in
the developers and cut down the frequency of releases, we have been able to
support replicating 200~300GB databases.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Dalibor Cvijetinovic" <dalibor@.ice.si> wrote in message
news:OC8DqnatDHA.2340@.TK2MSFTNGP12.phx.gbl...
> Is there anyone with some expirience in replicating such large database?
> Maybe some good link or something like that. I would need trans
replication
> instructions.
> regards,
> Dalibor
>|||Our amount of data that needs to be replicated is around 20-30GB. That is
the reason why I would like to change replication type.Currently I am using
snapshot/push replication. Our maintenance window is around 12 hours. But in
that time i must import some data which takes about 2 hours and then i do
snapshot/push replication of 130GB. That replication is lasting forever!!
After that i must replicate another db with 25GB.
I need to make trans replication or I will simply get ...
Furthere more this large scaled replication are not stable.
Can you give me some pointers on how to resolve this problem.
Dalibor
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:Ol$yrMbtDHA.424@.TK2MSFTNGP11.phx.gbl...
> If you have a fast link between your publisher/distributor/subscriber,
> replicating 130GB is still managble, especially when the amount of data
> changes is relatively small in comparison with the total database size. We
> are replicating bigger database than that with transactional replication.
> With 130GB of data, it could be a major headache to re-snapshot your
> publication, which may take a while in most environments. It can become a
> major problem when you don't have a large maintenance window. For us, the
> most common reason for requiring a new snapshot is new releases of the
> application that introduce database schema changes. Once we have reined in
> the developers and cut down the frequency of releases, we have been able
to
> support replicating 200~300GB databases.
> --
> Linchi Shea
> linchi_shea@.NOSPAMml.com
>
> "Dalibor Cvijetinovic" <dalibor@.ice.si> wrote in message
> news:OC8DqnatDHA.2340@.TK2MSFTNGP12.phx.gbl...
> > Is there anyone with some expirience in replicating such large database?
> > Maybe some good link or something like that. I would need trans
> replication
> > instructions.
> >
> > regards,
> > Dalibor
> >
> >
>