We recommend reviewing and updating objects in Slate to use current best practices. If you are encountering slow database performance, we recommend the following:

 1. Check your rules - Look at your rules to see if any rules are running particularly slowly or not at all, resulting in "ERR." Navigate to Check Rules within the Rule Editor to determine how long each rule takes to run. If rules are failing and returning "ERR," click on the Rule Log to view the errors. Ensure you are using best practices in rules. 

2. Review data imports - Review your data imports to see if any files have long load runtimes. Schedule data imports for low-usage times and break down particularly large files into multiple, smaller imports. Review Importing Data to confirm you are setting up imports using best practices.

3.  Navigate to the Job Activity Monitor tool- Use the Job Activity Monitor within the Database page to display the history and results of all query and report runs, including scheduled exports. Click into any rows that are marked as "failure" for more details. Review our recommendations on Scheduling Exports to ensure you have set up scheduled exports correctly. 

4. Review the Error Log - Navigate to the Error Log within Database to review any database errors. This will display the error message returned from particular methods and pages within Slate. Use the Definition of Common Errors to understand how to further troubleshoot these errors. 

5. Review the System Dashboard - Use the System Dashboard within the Database page to understand overall database performance and usage. This tool can be used in tandem when scheduling data imports for low usage times.  

6. Review your queries - Use our best practices to optimize queries for efficiency.

7. Consider your data and record management - Ensure your data is clean and accurate by frequently merging duplicate records in Consolidate Records. Review best practices and guidance on Consolidate Records to merge various types of records. Also confirm that the data and records you retain are necessary for your current processes. Remove extraneous data and records using the Retention Policy Editor, following our best practices.