By: Kory Salem On: March 02, 2017 In: Interactive Intelligence Comments: 0

If you want to preserve system performance and avoid possible service interruptions, maintaining a healthy reporting database is critical. For larger companies with dedicated SQL database administrators, this comes as no surprise. However, smaller companies often overlook SQL maintenance until the database begins to have problems responding. The telltale sign of a database performance issue is long run times for reports. If unaddressed, the issue will get worse until eventually requests will timeout altogether. Any part of the platform that uses the database can also be affected. That includes things like Interaction Recorder or Feedback.

The details of a SQL maintenance plan are fairly technical and best left to the folks maintaining those systems. The important point is to make sure someone is keeping an eye on your SQL server or it will eventually have problems.

For reference, here is a link to the IC Database Configuration and Maintenance for SQL Server Technical Reference:

If you’d like to learn how to check for index fragmentation, here is a link to a Microsoft Technet article:

Hope this information is helpful to you and your team. Thanks for reading!