Full Text Index in Designer.exe

Hi René,

have you allowed the Designer application database settings to save the database locally? (Database-> Settings -> Tab "Application" -> Designer database settings)?

Regards,

 Tino

Hi Tino,

Thank you for the tip. Yes, I have enabled the option and additionally, I have conducted a test by saving the location of the database to a separate directory (D:\temp\LocalDatabaseDesigner).

I noticed that upon starting the Designer, a file was created there with the name: Designer_TC5SAPc1qoBOSOCmNNPkH0tIVmbXYc.db with an initial size of 24,256 KB. Then, I updated the index, which as we know, always takes a few minutes.

The file was much larger afterwards, at 2,483,584 KB, but only after I closed the Designer, which is probably due to the indexed data.

When I restart the Designer and open the drop-down menu in the search, I do have the option “Update Index”. However, if I ignore this and simply search for the word “test”, I get the message “Initializing Full Text Search” in a modal popup window, and it takes as long as if the previously created index is no longer valid or can no longer be used.

In the past, it was the case that the index was sometimes not up-to-date, but you could then simply and quickly update the index with “Update Index”. Since v8.2 and still with v9.2, the option “Update Index” is no longer available when restarting the Designer, as if the Designer does not recognize the old index.

My expectation would be that if an index is stored in the local database, this index should be used when the Designer is restarted. If I then cannot find a script or something similar that I just created, I can quickly update the index myself.

Are we the only ones experiencing this problem?

Regards

René

Hi René,

yes the index is recreated every time. But usually this is done in a few seconds because its a local operation on the SQLite database.

Can you please check the following?

1. Is there any network traffic for the Designer in the Task-Manager when the modal popup windows is shown in the Designer? If so, the Designer completes the SQLite data and this can be slow.

2. Run "SELECT name, SUM(pgsize) table_size FROM dbstat GROUP BY name ORDER BY table_size desc" in the "Datatbase->Run SQL-Editor. Are there an huge tables that will explain such a long processing time?

Regards
Sylko

I checked the Designer code.

The reason for the busy time. The Designer has to load the text columns that are marked with IsBlobExternal = 1. And that can be a lot of data.

But yes. Recreating the index only if its really required is an option for optimization.

Regards
Sylko

I checked the Designer code.

The reason for the busy time. The Designer has to load the text columns that are marked with IsBlobExternal = 1. And that can be a lot of data.

But yes. Recreating the index only if its really required is an option for optimization.

Regards
Sylko