distribution agent works for one db but timed out for another db

Hi friends,
Can someone help me on this? I have set up transactional repl between the
primary site and secondary site for 2 databases. Both transactional repls are
bi-directional. Now the publication for one db works file but it did not work
for another db. The distribution agent was saying "time out expired" during
the initialization. I had modified QueryTimeout from 300 to 4800 which made
the subscriber's transaction log dramatically increase. My question is why it
works on one database but did not work on another one (this is bigger size).
both dbs stay on the same machines. Publisher and Distributor are the same
machine but the Subscriber is running on a separate one.
Thanks in advances,
Perhaps modify the LoginTimeout as well.
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
"FYK" <FYK@.discussions.microsoft.com> wrote in message
news:3F2213CE-63A2-45B8-A267-8E370F7CCEFC@.microsoft.com...
> Hi friends,
> Can someone help me on this? I have set up transactional repl between the
> primary site and secondary site for 2 databases. Both transactional repls
are
> bi-directional. Now the publication for one db works file but it did not
work
> for another db. The distribution agent was saying "time out expired"
during
> the initialization. I had modified QueryTimeout from 300 to 4800 which
made
> the subscriber's transaction log dramatically increase. My question is why
it
> works on one database but did not work on another one (this is bigger
size).
> both dbs stay on the same machines. Publisher and Distributor are the same
> machine but the Subscriber is running on a separate one.
> Thanks in advances,