Hi all,

I'm building a T-SQL solution to sync our saleslogix installation with our commercial system.

Part of this is updating the address table for customers with changed details.

I’m running into some performance issues as each insert / update statement I execute on the address table, fires the Address_Recchange trigger, which update the slxrecchange table.

This is causing a few million transactions to occur, log files growing ‘till I run out of hdd space on the server, db admins screaming at me, fire, crumbling of society, general apocalyptic chaos etc.

I can fix this through disabling the trigger, executing my batch update and re-enabling the trigger. I have tested this and all works well.

My questions are            1.) What is the slxrecchange table for?

 2.) Is there any issue with not executing the trigger on this update? Iif yes, can I just fire the trigger on the final record in my list to record a change?

This table was introduced for Exchange Link, so as long as you are not using it, you should be ok disabling this trigger.

Also, as you stated, this table doesn't get maintained.

I have not ran latest version of Exchange Link, but from what I recall it never deleted any records. If a change ocurred for an existing record, it updated the Modify date for that record). In my mind this is ok for small Databases, but could be quite a problem on a larger Database.

Bottom line, untless you are using Exh Link, then you should be able to just completely disable this trigger and clear this table.

Thanks Raul

Hi Again Raul,

i've just checked with our Saleslogix expert, he says we are running the Exchange link.

So do you know if it will be a problem if i:

1. disable trigger.

2. run update statements

3. enable trigger.

Apart from if someone tried to run an update external to my process at the same time while i had the trigger disabled, would it matter if I havent indicated a change in the table?

cheers

The trigger is used to maintain the contact detail for ExchangeLink such that contacts details are kept in sync. Disabling the trigger and re-enabling it will, of course, negate that - so it rather depends on what your update does as to whether it has an effect or not. If you're not using Contacts as part of the sync (check with your SLX person) then you can just disable the trigger entirely (remembering to re-enable it later if you then choose to sync contacts).

The trigger is used to maintain the contact detail for ExchangeLink such that contacts details are kept in sync. Disabling the trigger and re-enabling it will, of course, negate that - so it rather depends on what your update does as to whether it has an effect or not. If you're not using Contacts as part of the sync (check with your SLX person) then you can just disable the trigger entirely (remembering to re-enable it later if you then choose to sync contacts).

Quote: Originally posted by Paul Hi Again Raul, i've just checked with our Saleslogix expert, he says we are running the Exchange link. So do you know if it will be a problem if i: 1. disable trigger. 2. run update statements 3. enable trigger. Apart from if someone tried to run an update external to my process at the same time while i had the trigger disabled, would it matter if I havent indicated a change in the table? cheers

The problem with disabling the Trigger is that you won't have your Changes synched out via Exchange Link. So, if you updated Addresses in SLX via this script, then Exchange Link won't send those changes out to Outlook.

Thanks Guys,

Sounds like i'll need to keep the triggers in place.

I'll strip the address checking functionality out and run it seperatly,

I think I  was updateing when i didn't need too, I was updating the whole record based on changes in the  Account table, which includes sales data, so i was updating the address if sales had changed.

I'll strip the address component out and do it sepeartly when there is a change.

Cheers!