April 24, 2007 at 6:54 am
Hi Guys,
In my company, the database structure like:
Database A replicated data into database B using transaction replication. In
database B, there are some triggers on the tables which have subscription on
them. the triggers put data that replicated from Database A into anther table
A. then the client aqpplication retrieve data from the table A.
Today, we got problem that client populated data in database A very large,
which caused replication and triggers worked very long and slowed down the
database, as well as it blocked the client application to retrieve data from
table A. we cannot put nolock in the client application because this is a
critic application and don't allow error occured. I wonder if there is a way
that can optimize the database so that it doesn't slow down the database when
large bulk data are input in the database A. Can someone give me suggestion?
Thanks.
April 26, 2007 at 1:37 am
Hi,
So are the Triggers on DB B triggering data to a Table on DB b or DB A
Graeme
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply