Hello,
Merge Replication, SQL Server 2005
I have got a table with an update trigger that is supposed to fire when a
user updates a field.
When replicating this database, the trigger fires when a user updates a
field *and* when the update is performed by the replication process.
How can I avoid the latter? Is there a TSQL-function to distinguish the two?
Thanks for your effort, Wolfgang
Another way is to hack into the sessionproperty
ie if ('replication_agent') <> 1 then its a user action.
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
"Wolfgang" <Wolfgang@.discussions.microsoft.com> wrote in message
news:168538E7-89A2-45F3-ABD6-566F2C4B3760@.microsoft.com...
> Hello,
> Merge Replication, SQL Server 2005
> I have got a table with an update trigger that is supposed to fire when a
> user updates a field.
> When replicating this database, the trigger fires when a user updates a
> field *and* when the update is performed by the replication process.
> How can I avoid the latter? Is there a TSQL-function to distinguish the
> two?
> Thanks for your effort, Wolfgang
sql
Showing posts with label 2005i. Show all posts
Showing posts with label 2005i. Show all posts
Tuesday, March 27, 2012
Wednesday, March 21, 2012
Dist Agent Setting
Running Win 2003 & SQL 2005
I had a problem with one of my dist agents & got backed up to the tune
of 1.55 million commands in the distribution database waiting to be
applied.
The agent has been running for 9+ hours and the number of pending
commands has not changed.
Is there a setting I can chang/make in the dist agent to get them to
process faster or atleast see the number of pending go down, so I will
know it is working.
AHIA,
Larry...
Larry - you could try reducing the -CommitBatchSize
nd -CommitBatchThreshold parameters and see if this helps.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
I had a problem with one of my dist agents & got backed up to the tune
of 1.55 million commands in the distribution database waiting to be
applied.
The agent has been running for 9+ hours and the number of pending
commands has not changed.
Is there a setting I can chang/make in the dist agent to get them to
process faster or atleast see the number of pending go down, so I will
know it is working.
AHIA,
Larry...
Larry - you could try reducing the -CommitBatchSize
nd -CommitBatchThreshold parameters and see if this helps.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Subscribe to:
Posts (Atom)