Replication issues with multiple databases

I am planning to use replication from 400 databases to the master database on
a periodic basis. Do you see any issues with that ?
All databases have the same structure
Alu,
this is a bit vague as it stands but certainly this is 'possible'. In
this link they discuss scaling merge to 2000 subscribers:
http://www.microsoft.com/technet/pro...mergperf.mspx.
For your setup, the type of replication selected will have some
implications. There are also implications with the type of topology
selected, hardware available, bandwidth, data volume etc so really you just
have to implement it, monitor using Perfmon and then see how it goes. As an
aid to avoid contention (data and disk) you might need to consider
staggering synchronization.
Regards,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication Issue

We have replication set up from master sql server to 4 other sql
servers. Replication is transactional and 4 other sql servers are
subscribers and master database is publisher. The issue we are facing
is on subscriber database , the tables sometimes gets blocked and the
query times out. But if we query it again or refresh the page(that
sends the query again) it works fine.
Can it be because of some configuration issues with replication that
it holds the table until it replicates data into it.Rahul,
The problem may be that your query is acquiring shared locks on the same
data that replication needs to update. For querying subscriber data, you can
use the NOLOCK or READPAST hints in your queries. Don't attempt to update
any replicated data directly; use updating subscribers if you want to do
that.
Ron
--
Ron Talmage
SQL Server MVP
"Rahul" <rahulkhushoo@.yahoo.com> wrote in message
news:246c8d90.0311071425.204116e6@.posting.google.com...
> We have replication set up from master sql server to 4 other sql
> servers. Replication is transactional and 4 other sql servers are
> subscribers and master database is publisher. The issue we are facing
> is on subscriber database , the tables sometimes gets blocked and the
> query times out. But if we query it again or refresh the page(that
> sends the query again) it works fine.
> Can it be because of some configuration issues with replication that
> it holds the table until it replicates data into it.