If you have a Dynamics 365 Online system where you have very customized entities with a large number of columns, 200+, you can experience SQL timeout errors coming from the Dynamics 365 system when attempting to replicate the data using a Scribe Online Replication Solution.  These timeouts may be generated because the source entity datetime field Scribe Online uses to locate new and updated records is not indexed.  If the field is not indexed, the query operation has to search through all of the records to locate the correct set for replication.

For example, assume your Account entity has 300 columns because customized fields were added.  Scribe Online needs to query the Account entity for new and updated records, but the ModifiedOn field is not indexed. Instead of starting with the first new or updated record and working from that point forward, the query operation has to check the date on every single record.  As more data is added and edited, the query operation takes longer and longer, causing timeouts with errors similar to the following:

Message: Execute process failed: 
Exception Type : FaultException`1 
Message : SQL timeout expired. 

 

Replicating Dynamics 365 data where entities are customized and have a large number of columns can sometimes generate SQL timeout errors.

Contact your Microsoft representative to add an index to the ModifiedOn field.