We have reached the point at which something seems to be problematic...the following issue:
we perform a search for a record - such as a company or contact in a company. start typing the letters and nothing comes up (for example, Arizona). a little while later we try again and sure enough there are many entries beginning with or including the word Arizona. Same thing for others.
This is problematic because someone might do this, think a record does not exist, enter it and later find multiple entries. Also, it makes finding things extremely difficult.
On various occasions, when we sign into clay and open a window to perform a search the filter values simply do not populate. After closing and reopening such a search window, then the filter values appear.
Also, after selecting a record appearing in the filter values, it takes a long time for the actual records to come up in the search results.
Are these things all related? What could be the issue? It is really affecting our work now significantly. THanks.
To register for the forums, please contact your Digital-Clay representative.
Search Mechanism
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Search Mechanism
(Is this related to the older issue? http://digital-clay.com/community/forum ... f=11&t=800)
When you say that results don't come up: Are there any values BEFORE you start searching? If not (or even if there are only a couple of recent entries instead of the full list), then it is simply a matter of the list not being populated yet. There are a couple of things to check if this is the case.
As far as actual results taking a while, this may be related if there is a general slowness problem with your system. Solving a slowness issue can be anything from moving from MDB to SQL Server, performing a maintenance task on your database, adding an index, moving to a faster server, or troubleshooting networking problems.
When you say that results don't come up: Are there any values BEFORE you start searching? If not (or even if there are only a couple of recent entries instead of the full list), then it is simply a matter of the list not being populated yet. There are a couple of things to check if this is the case.
As far as actual results taking a while, this may be related if there is a general slowness problem with your system. Solving a slowness issue can be anything from moving from MDB to SQL Server, performing a maintenance task on your database, adding an index, moving to a faster server, or troubleshooting networking problems.
Re: Search Mechanism
Correct, it is related to the older issue and has simply expanded or at least been more noticeable.
There are cases in which the values do not appear before searching. Usually we then close and reopen the window and magically there are values there. Not sure why recently though the list is not being populated and then when we select a particular record it can take a long time (like 20-50 seconds) for the record to open.
For moving servers, adding indexes, etc. we will need assistance - we would not handle that without involvement from Digital Clay. We could have our computer service provider check issues with networking if you can tell us what to check. Other than Digital Clay, we have not noticed/experienced general network or slowness issues - just Digital clay.
what do you suggest to do next/first?
There are cases in which the values do not appear before searching. Usually we then close and reopen the window and magically there are values there. Not sure why recently though the list is not being populated and then when we select a particular record it can take a long time (like 20-50 seconds) for the record to open.
For moving servers, adding indexes, etc. we will need assistance - we would not handle that without involvement from Digital Clay. We could have our computer service provider check issues with networking if you can tell us what to check. Other than Digital Clay, we have not noticed/experienced general network or slowness issues - just Digital clay.
what do you suggest to do next/first?
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Search Mechanism
Well it sounds like the filter list is simply taking a while to populate along with everything else. i.e. general slowness.
When you click on the filter, normally it should take a second or less to populate (i.e. wait before searching for anything until the list populates - it will fill on its own).
Some initial stuff:
- For slowness, are you on MDB or SQL Server? If MDB, it may be time to switch (contact your Clay rep for help on this).
- Do you know what a database maintenance action is? I think we talked about this once. It helps optimize the database for speed issues.
- To rule out networking issues simply connect on the same machine as ClayCentral using a Clay client and connect to 'localhost' when logging in.
- I would also check that the server where ClayCentral is running isn't running slow, low on memory, or too busy running many other things.
When you click on the filter, normally it should take a second or less to populate (i.e. wait before searching for anything until the list populates - it will fill on its own).
Some initial stuff:
- For slowness, are you on MDB or SQL Server? If MDB, it may be time to switch (contact your Clay rep for help on this).
- Do you know what a database maintenance action is? I think we talked about this once. It helps optimize the database for speed issues.
- To rule out networking issues simply connect on the same machine as ClayCentral using a Clay client and connect to 'localhost' when logging in.
- I would also check that the server where ClayCentral is running isn't running slow, low on memory, or too busy running many other things.
Re: Search Mechanism
1)As far as we are aware, we are using MDB still so we will be in touch with the representative. You also mentioned that before.
2)Yes, we talked about the database maintenance and as a result every week the system does it.
3)tried opening on server where Central is located. overall the system seems faster with regard to the searches and items coming up. Will do more testing. At the moment, records are coming up much faster.
4) Ok, we'll need to check the server.
2)Yes, we talked about the database maintenance and as a result every week the system does it.
3)tried opening on server where Central is located. overall the system seems faster with regard to the searches and items coming up. Will do more testing. At the moment, records are coming up much faster.
4) Ok, we'll need to check the server.