Error: SQL Timeout

Solution

The most likely cause is that some SQL tables have grown too large, specifically EventLog, SiteLog, and ScheduleHistory.

1. Go to Persona Bar > Settings > SQL Console.
2. Check the sizes of EventLog, SiteLog, and ScheduleHistory.
   1. Run the following SQL script:

      
      SELECT t.NAME AS TableName
      	,p.rows AS RowCounts
      	,SUM(a.total_pages) * 8 AS TotalSpaceKB
      	,SUM(a.used_pages) * 8 AS UsedSpaceKB
      	,(SUM(a.total_pages) - SUM(a.used_pages)) * 8 AS UnusedSpaceKB
      FROM sys.tables t
      INNER JOIN sys.indexes i ON t.OBJECT_ID = i.object_id
      INNER JOIN sys.partitions p ON i.object_id = p.OBJECT_ID
      	AND i.index_id = p.index_id
      INNER JOIN sys.allocation_units a ON p.partition_id = a.container_id
      LEFT JOIN sys.schemas s ON t.schema_id = s.schema_id
      WHERE t.NAME NOT LIKE 'dt%'
      	AND t.is_ms_shipped = 0
      	AND i.OBJECT_ID > 255
      	AND t.name in ('ScheduleHistory', 'EventLog', 'SiteLog')
      GROUP BY t.NAME
      	,s.NAME
      	,p.Rows
      ORDER BY TotalSpaceKB DESC
                                          

   2. In the result, note the RowCounts values for EventLog, SiteLog, and ScheduleHistory.
3. Clear EventLog.
   1. Run the following SQL script:

      
      DELETE TOP (1000)
      FROM EventLog;
                                          

      Note: To clear EventLog, replace 1000 with the RowCounts value. To reduce the size of EventLog (instead of clearing it), replace 1000 with the number of rows you want to delete.
4. Delete the SiteLog and ScheduleHistory tables.
   1. Run the following SQL script:

      
      TRUNCATE TABLE SiteLog;
      TRUNCATE TABLE ScheduleHistory;
                                          

5. Restart the application to allow the changes to take effect.

Testing

1. Access the Admin Logs