Company -> Blog...

December 23rd, 2015 by

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.

http://www.simplesoft.net/blog/wp-content/uploads/2012/11/SS-Border.png

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

Comments Off on Saleslogix Speedsearch Truncate the IndexUpdates Table


 

 

October 31st, 2014 by

Infor CRM (formerly Saleslogix) has this terrific engine called SpeedSearch that works behind the scenes and helps to index entities. The indices and structure is based on a third-party searching and indexing engine called dtSearch.  The main idea is that it provides high performance searching so that a user can perform a Keyword search and Saleslogix returns records based on that keyword.  It is well designed, integrated, and works well when it is properly configured and managed.   SpeedSearch comes in two flavors: Standard and Advanced licensing.  The main difference with the Advanced licensing is the ability to add and customize, which is outside of this discussion today.

The secondary function is that SpeedSearch helps to identify duplicates on imports using the lead import tool.  Speedsearch works in both the web and windows without any differences in result sets, as expected!  If there is one area of the tool that I would be critical of,  it is what I would call default madness.   This article is dedicated to helping administrators review the setup and configuration to make sure that they have reviewed and optimized the settings for SpeedSearch.  The various settings can have a huge impact to your end user experience.

First, we need to evaluate where you are with Speedsearch configurations and operations in place.  Is the SpeedSearch service running today?  Are indexes enabled and being run successfully?  Are they all set to the default of 12:00 AM?  Are the indices matched to the areas of your usage?

  1. Start | Run | Services.msc  and confirm the service is running
  2. Start | Program Files | Saleslogix | SpeedSearch Configuration  and confirm the basic configurations
    1. Check the servername,  Share Path,  and database options
    2. Start | Program Files | Saleslogix | Administrator | Menu for Manage | SpeedSearch Indexes…
      1. Confirm the indexes enabled
      2. Start | Program Files | Saleslogix | Administrator | Menu for Manage | SpeedSearch Configuration… | Schedule tab
        1. Confirm the jobs are running and which jobs are needed
        2. Table Check:  Select count(*) from sysdba.IndexUpdates to make sure that SpeedSearch is cleaning up changes after the index jobs are being ran.

Once SpeedSearch has been reviewed and confirmed operational, we have a few recommendations for optimization.

Top Recommendations:

Only index areas that are required for Infor CRM (Saleslogix) and areas of Infor CRM (Saleslogix) that are being used.  If you are not using defects for instance, turn off the index.

Only schedule the type of index jobs, adding change differences, for the areas required.   For instance if you are indexing Account, but you only need to see updates on a daily or weekly basis, then delete the incremental jobs.

If there are schedules for areas that are not being used (like defects mentioned earlier) delete them and make sure they are not enabled.

Stagger the times that the index build runs.  By default, they are set to run at 12:00 AM and if all the indexes are running at the same time that is not optimal and may cause issues.

So now you have evaluated SpeedSearch, thought through the changes to make, and lastly you need to schedule time to make the changes and confirm the results.  You will need to pause the services, make the changes, and turn the services back on.

Finally, you will need to monitor two areas.  First making sure the services are running properly and secondly the jobs are cleaning up the speedsearch tables properly.

Don’t dwell on what went wrong. Instead, focus on what to do next. Spend your energies on moving forward toward finding the answer.

Denis Waitley

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 Users Group Events.

http://www.simplesoft.net/blog/wp-content/uploads/2012/11/SS-Border.png

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

Comments Off on How to Optimize and Cleanup SpeedSearch for Indexing Infor CRM (Saleslogix) Searches


 

 

 


scroll up

Hit Counter by technology news