At times I have been asked how can I increase the performance of SalesLogix. For systems using SQL2005 or SQL2008 the slowdown may be corrected by adding an index to the table that the SalesLogix script queries. The trick is finding where the bottleneck resides. My suggestion is to use the SLXProfiler when a significant slowdown occurs and record the sql logs. Then examine those logs for queries that take significantly longer. For example, one query on the history table was taking 871.3167 milliseconds to execute while the average time for other queries on history table were under 5.0 ms. How do we improve this performance lag? One way is to minimize the amount of history distributed to remote users and another way is a custom index. Next week’s topic will discuss the steps to create that index.
- Creating or Updating Records Using the Entity Class in Creatio
- Column Names to Avoid and Build Errors for Object Entities in Creatio
- How to Create a Filter to View the Active Marketing Contacts in Creatio
- Issue with saving Date Criteria in the InforCRM Query Builder version 184.108.40.206
- Conditionally Making a Detail Read-Only in Creatio