Search the Knowledgebase Browse by Category
Searching is very slow to respond ...or... A recipe appears in the default list, but doesn't appear when searching by name.
User Opinions
100% thumbs up 0% thumbs down (4 votes)

How would you rate this answer?
Helpful
Not helpful
In certain cases (sometimes after an update has been installed), the log file associated with the ESHA Database becomes damaged or corrupted, causing searching in the program to be unreliable.  In this scenario:
  1. Close your ESHA software.
  2. On the server which hosts your database, launch Database Utility (found in the Windows Start menu, under ESHA).  If your operating system is Windows Vista, Windows 7 or Windows 2008 Server, there is need to right-click the shortcut and choose Run As Administrator for Database Utility.
  3. Connect to the SQL Server & database.
  4. Backup the database.
  5. After backup, click Database / Shrink.
  6. Exit Database Utility.
After the above, launch your program try searching again.

Advanced: If using your own instance of SQL Server, or you have SQL Server Management Studio (Express) installed (a free download from Microsoft), you can force a rebuild of certain indexes which may help searching.  Specifically:
  1. Using Management Studio (Express), connect to the proper SQL server instance, and open the ESHA Database.
  2. Expand Tables.
  3. Expand BaseFoodName table.
  4. Right-click the Indexes listing, and choose Rebuild All.
  5. Click OK to the Rebuild Indexes dialog.
  6. Exit Management Studio (Express).
Attachments
No attachments were found.
Related Questions
No related questions were found.

Powered by ActiveKB Knowledgebase Software