There are several optional features in Time Matters that can greatly effect your performance. As you may remember, we previously covered "Keyword Indexing" in Step 2. In that article we learned that you could simply disable the option and immediately recover the performance benefit. Not all features are as simple and obvious to recover from disabling. Case in point: the Time Matters Exchange Synchronization.

Disabling the Exchange Sync service or uninstalling the Exchange Synchronization Utility does not stop the ongoing database activities that are started when you install the Exchange Sync. The Exchange Synchronization adds nine database triggers to your Time Matters Database. Three triggers in each of the following tables: Contact, Event and ToDo. These database triggers perform extended data updates each time one of these tables is modified. That means if your Events and ToDo's are "following" you are performing one modify for the Event (or ToDo) table and two actions are initiated from the update trigger, one delete, one insert. Throw in the database maintenance, calculated field activity and the transaction log updates and you can quickly aggregate significant resource consumption.

I mentioned Calculated Field activity. Calculated fields that are based on the Record Date must be recalculated when the Follow process changes the record date. These calculations are NOT ran in the stored procedure but rather a unique second process is spawned after Time Matters is initialized. This process will "recalculate" Calculated fields for each record type. Once again causing multiple database updates for each affected record.

In summary, if you uninstall the Exchange sync make sure you finish the process by manually removing the after effects of the original installation. A new "Exchange Sync Status" test was added to SharpShooter version 1.14 to report the status of a given database's Exchange Sync.

• < Prev
• Next >