Dear Paul,

Its seems our indexupdates table is growing.  What can be done?

Although this is an older issue and now corrected, you should still monitor the table to make sure that the indexupdates table is cleaning up after itself.

There are a few short steps for the potential resolution (the steps can be time consuming but they are not difficult) with SpeedSearch rebuilding.  I have some standard disclaimers because Speedsearch is very heavy on the Disk I/O and needs to be performed off hours when users are not on the system.  The steps below are easy but could take a long time to run depending on the amount of records in the database especially the history table.

• First, backup your production Saleslogix database.
• Second, truncate your indexupdates table.
• Third, rebuild the indexes.
• Fourth, test the results.
• Lastly, communicate the results of the work.

Let’s review more details below ( I have a few more details than above):

My Standard Disclaimers apply.

==========================================

1. Kick off the users.
2. Perform work off hours.
3. Back up your database with verify options.
4. Run the truncate table command on the indexupdates table.

Open up SQL Query analyzer, change the <Saleslogix Database Name>; to the name of your saleslogix database name and remove the <> characters and verify the following.  The Infor CRM (Saleslogix) kb article had the table name singular, but I believe it is plural, so correct me if I am wrong.

USE <Saleslogix Database Name>;

GO

SELECT COUNT(*) AS BeforeTruncateCount FROM sysdba.indexupdates;

GO

TRUNCATE TABLE sysdba.indexupdates;

GO

SELECT COUNT(*) AS AfterTruncateCount FROM sysdba.indexupdates;

5. Stop the speedsearch service

6. Go to the Saleslogix Speedsearch folder with the Speedsearch indexes

Go to the SpeedSearch share folder as noted in the SpeedSearch configuration

7. Remove /backup the contents of each folder  (Note: not the folders themselves)

8. Start the Saleslogix speedsearch service

9. Login to the administrator as admin user

From the menu, Manage SpeedSearch Configurations

Schedule tab

Rebuild all the Full indexes

Rebuild all the incremental indexes  (this could take a while)

10. Test the results in the Saleslogix client/Web client or using SpeedSearch client in the network client.

11. Communicate the test results back to operations as needed.

Going forward it is good practice to review and optimize the Speedsearch index schedules to confirm they are running at staggered times. E.g. not all running at 12:00 AM, 6:00 AM which is not optimal, but is the typical default.  You may also have indexes running for areas that are not being used as well.  Speedsearch is a great tool and works well, but needs to be monitored and optimized.

Be sure you put your feet in the right place, then stand firm.

– Abraham Lincoln

If you would like to discuss upgrading your system, or to see a free demonstration, please contact Simplesoft Solutions.

Remember to check our CALENDAR and register for free training, demo sessions, and the Heartland Saleslogix Users Group Events.

Dayton/Cincinnati, OH | Charleston, WV | Charlotte, NC