Hilary Cotter wrote:
> I would use transactional replication as it offers the lowest latency.
>
> --
> Hilary Cotter
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
>
>
> "AK" <arshad.khan@policyadmin.co.uk> wrote in message
> news:1163424096.157922.228010@k70g2000cwa.googlegroups.com...
> > Hello All,
> > I am a newbie dba and need some expert advice on one of my development
> > scenario I am currently struck with. I am in process of designing a
> > reporting solution for my company. It is going to be a web based
> > intranet thin client multitiered application using sql server 2000 and
> > .net platform.
> >
> > This application basically shows the real time KPI's or statistics in
> > different forms of reports on an hourly basis to the senior managers to
> > right on their desktop. Eventually these reports will help them in
> > decision making for the better performance of the business...
> >
> >
> > My question here is what is the best way of transferring large chunk of
> > data (not entire table(s)) from production server (SQL 2000) to a
> > reporting server or staging database with an hourly refresh without
> > stressing the production environment?
> >
> > Is it a) Replication preferably snapshot? Or
> > b) BCP? or
> > c) DTS?
> > Or do you suggest any better way of achieving this task?
> >
> > Any suggestion or tips would be greatly appreciated.
> >
> > Looking forward for your responses.
> >
> >
> > Many Thanks,
> >
> > AK
> >