This is definately looking more like replication only solution. Only problem
"Mike Epprecht (SQL MVP)" wrote:
> Hi
>
> Replication has a lot of overhead as the data is moved at record level.
>
> Log shipping is the same as backup and restore. During the period the log is
> being applied on the destination server, you can not access the DB.
>
> What are you trying to achieve? A Reporting Server, a hot backup?
>
> Regards
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@epprecht.net
>
> MVP Program:
http://www.microsoft.com/mvp >
> Blog:
http://www.msmvps.com/epprecht/ >
> "Burningcoals" <Burningcoals@discussions.microsoft.com> wrote in message
> news:188A57BD-9CAB-4BD6-A605-11A4D502D427@microsoft.com...
> > I was looking into replication, but I didnt want to get into having to
> > rebuild replication everytime we updated our Database.
> >
> > I really just need to setup a read only mirror. I was looking into LS (Log
> > Shipping) and that doesnt seem like it would work that great. Since I need
> > our mirror able to be accessed with as little latency as possible.
> >
> > What is the best model to use for a SQL read-only mirror that could be
> > updated real-time or close to it? I think the only thing I can do this
> with
> > is replication, possibly Trans-Rep? Or even backup/Restore, although I am
> > doing this to offload some builds for performance reasons. So
> backup/restore
> > would have a performance hit on the server.
> >
> > Thanks for any info.
> >
> >
>
>