...
Check the EngageIP Event Log (Reports tab > Event Log) to see if any major activity is occurring (billing, credit card processing, etc.)
Determine if any reports are being run which can temporarily tie up system resources (Accounting personnel running an aged report for example)
Determine if any jobs are in the job queue which the EngageIP is processing (Reports tab > Jobs). If so ensure performance issues do not continue when jobs are complete
Ensure EngageIP Services are running and operating normally. E.g. if the Event Service is running but workflows are not executing or emails being sent then restart the Event Service. For more information on EngageIP Windows Services see the EngageIP Windows Services Overview article
Configuration Tweaks:
...
Open Studio Management
Click the 'New Query' button
Then paste in the SQL below and select the appropriate database (typically named 'boss')
Code Block USE BOSS --Enter the name of the database you want to reindex DECLARE @TableName varchar(255) DECLARE TableCursor CURSOR FOR SELECT table_name FROM information_schema.tables WHERE table_type = 'base table' OPEN TableCursor FETCH NEXT FROM TableCursor INTO @TableName WHILE @@FETCH_STATUS = 0 BEGIN DBCC DBREINDEX(@TableName,' ',90) FETCH NEXT FROM TableCursor INTO @TableName END
Update the database name in the query if its not ‘boss
Execute
Note: this query may take several minutes, wait until it's complete and then review invoices / the interface to determine if there is any performance improvement
...
UDR Records on a system may take significant amounts of space. For usage, the file EngageIPUDRFILEGROUP.ndf may get very large. This is a data storage format file for SQL server which houses data related to the UDR table in the EngageIP database. If this file gets large, you will need to purge / archive UDR data. Please contact LogiSense for details on archiving data or reference this article: https://developer.logisense.com/archiving-old-records-udr-system/