Replication to SQL 2005

Hello all,
We have merge replication setup between 3 servers. SQL1, SQL2 and SQL3.
We have installed SQL2005 on a ReportingServer and want to be able to
popluate the database on SQL2005 with data from SQL1. How can we set this up?
We want to avoide setting up the whole replication process again as the
database is 25 GB and SQL3 is updated via a telephone line.
Thanks
Regards
Ishan
Ishan,
if the ReportingServer is RO apart from the replication synchronization, I'd
use transactional replication. I'd also consider dong a nosync
initialization to set things up with a database of this size.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication in 2005

We need to push all the changes across network to a secondary, reporting
server, on a timely manner. We were using replication in SQL200, but it
takes a lot server resources. Any new feathers in SQL2005?
There are a lot of new features in SQL 2005. Transactional replication will
place fewer locks on the publisher by default during snapshot generation.
You could also look at database snapshots or log shipping for this.
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
"awan" <awan@.discussions.microsoft.com> wrote in message
news:5D8A9D21-2AF4-4EB7-AAFA-603FCDA399FA@.microsoft.com...
> We need to push all the changes across network to a secondary, reporting
> server, on a timely manner. We were using replication in SQL200, but it
> takes a lot server resources. Any new feathers in SQL2005?