8.1 SNC02 Trigger Issue

[MikeSpragg]

Thanks Paul, my ultimate concern would be something like Replace Data, Imports etc. all starting to fail due to the triggers now in place. Things may start to get a bit messy & quickly with sites if they don't realise the impact if the triggers.

[RJLedger]

Thanks Paul!

Since the vast majority of folks do not have X3.. then which ones can we safely shut down (and not turn on again)..?

[pzeimet]

The Account triggers are currently only use by X3.  All others are needed for Outlook and Google Integrations.

Thanks

[RJLedger]

Thanks Paul,

 It's important that we group the triggers so that we can shut down all the ones that do not apply to a given installation.

Is there a further break between Google and Outlook integrations?

Also.. I assume the EL (current ones) were not included.

[pzeimet]

RJ, the Outlook and Google triggers are the same.  You are correct, I did not include the EL triggers since they are an add-on and not part of base.

Thanks

[pzeimet]

Thanks Mike, I will definately take this under consideration.

[RJLedger]

Thanks Paul. This will help us all big time!

[nraddatz]

Thanks guys for the very informative discussion here. We were also bit by the contact triggers on batch updates to Contact table (1.8 million+ rows, I guess we could have waited until christmas 2043 before they would finish...if they finished at all, since the log file was growing like crazy). This is a big one, and i'm not sure the triggers have been "publicized" properly, at least we were not aware of them, and we have quite a bit of experience in Saleslogix 8.x environments...

[greensweater]

I'd like to throw in my two cents to mention that the new triggers caused some problems for us when using 3rd party tools to do data imports. We couldn't figure out why our ETL was on track to take several days based on the throughput we were seeing until we disabled the triggers. A big fat gotcha when doing an import.

[RJLedger]

IMHO - we have just touched the tip of the iceberg when it comes to the performance problems being caused by (all these) OOTB SQL triggers.

There's just three choices right now:

    A - Have Outlook integration and suffer from the SQL triggers

    B - Drop Outlook integration and have a system that just might work as well as it did in the past.

    C - Hope Saleslogix/Swiftpage will com up w/a solution... soon!

Anyone?