"Michael Hotek" <mhotek@nomail.com> wrote in message
news:enjxwTvLEHA.556@tk2msftngp13.phx.gbl...
> Nope. I'd suggest doing what I outlined for several other customers.
Setup
> a transactional publication against that data on your publisher and then
put
> a subscriber on another machine where you users can run reports.
>
> --
>
> Mike
> Principal Mentor
> Solid Quality Learning
> "More than just Training"
> SQL Server MVP
> http://www.solidqualitylearning.com
> http://www.mssqlserver.com
>
>

"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:%23xspWMvLEHA.3348@TK2MSFTNGP09.phx.gbl...
> Tina,
> it really depends on the overall load. You can make life slightly easier
> having a remote distributor, but in your case I'd advise log-shipping to
> another server for reporting requirements. This way the report data
creation
> has no real impact on the production server, as logs are normally created
> anyway, rather than having another merge agent active all the time.
> HTH,
> Paul Ibison
>
>

"Michael Hotek" <mhotek@nomail.com> wrote in message
news:uCSnfHCMEHA.1192@TK2MSFTNGP11.phx.gbl...
> OK, but remember this, everything is hard coded. If you run out of
> resources on the publisher and need to move the distributor to another
> machine, you will have to completely remove replication from ALL machines
> and completely redeploy from scratch. Doing that with 1 - 2 machines is
bad
> enough, trying to do it with 250 machines when you have an environment
> deployed that everyone is using is an entirely different matter
altogether.
> Not saying it can't be done, but replication is one thing you don't do
last
> minute planning on and survive to tell about it.
>
> --
>
> Mike
> Principal Mentor
> Solid Quality Learning
> "More than just Training"
> SQL Server MVP
> http://www.solidqualitylearning.com
> http://www.mssqlserver.com
>
>