We have noticed that recently (perhaps since the last update but seemingly also before that), the system seems to hang quite a bit even when performing simple queries like looking for 1 or more records and outputting a document template to WORD. It has not done that before. In general, the system takes a long time to react and to move to subsequent steps.
Any suggestions for what might be the problem?
To register for the forums, please contact your Digital-Clay representative.
Hanging
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Hanging
I'm going to need a more detailed description of 'hanging'. A freeze of the client or just a slow response? For how long? Which specific tasks? Every single time you run that task? What about other similar tasks any of them not 'hanging'? All users (on different machines)?
Also make sure you are performing regular database maintenance (there is a database maintenance automation action). If the database has become unoptimized this would be enough to cause slow responses.
Also make sure the server machine isn't busy for some reason (CPU/networking).
Also make sure you are performing regular database maintenance (there is a database maintenance automation action). If the database has become unoptimized this would be enough to cause slow responses.
Also make sure the server machine isn't busy for some reason (CPU/networking).
Re: Hanging
It just takes more time - we see the little circle icon going around and around when it is over the filter results box. Eventually the data comes up.
Let us do some more investigation here. Indeed, we have not had a database maintenance automation action running -- we can set it up now. How often should it run - once a week? In the schedule interface, there is also a place to enter "Hour" - What should be filled in here?
Thanks.
Let us do some more investigation here. Indeed, we have not had a database maintenance automation action running -- we can set it up now. How often should it run - once a week? In the schedule interface, there is also a place to enter "Hour" - What should be filled in here?
Thanks.
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Hanging
Answering the other questions would help narrow it down....
Regarding the automation, just run it in the middle of the night. I would do it once a week during the weekend. May get away with running it once a month if the database is large. You should run it once manually tonight as well to see if it helps.
Regarding the automation, just run it in the middle of the night. I would do it once a week during the weekend. May get away with running it once a month if the database is large. You should run it once manually tonight as well to see if it helps.
Re: Hanging
On multiple computers, we are still noticing when conducting searches that it will take around 15-20 seconds before the item or records selected in filter values appears in filter results. In the meantime, when the mouse is over the filter results, we see the moving circle (showing that it is thinking...).
On another note, we have started to notice some interested issues with the filter/search mechanism. For example, when searching for Phoenix Technologies which is in the system, I typed in the search box each letter progressively of Phoenix. Phoenix Technologies does not appear until the search box has the full word Phoenix plus a space. Should it not show up as each letter is typed like the other records beginning with the word Phoenix which do show up?!
Similarly, the record "TME - Target for Medical Equipment" does not appear when the letters of Target are inputted or when the space is added. Only after typing "Target f" the entry appears.
If this is "normal" could you please explain how the algorithm works so that we can search properly? We have been under the understanding that when we enter letters in the search box, any record names which include the letters entered in the search box are supposed to appear in the filter values box.
On another note, we have started to notice some interested issues with the filter/search mechanism. For example, when searching for Phoenix Technologies which is in the system, I typed in the search box each letter progressively of Phoenix. Phoenix Technologies does not appear until the search box has the full word Phoenix plus a space. Should it not show up as each letter is typed like the other records beginning with the word Phoenix which do show up?!
Similarly, the record "TME - Target for Medical Equipment" does not appear when the letters of Target are inputted or when the space is added. Only after typing "Target f" the entry appears.
If this is "normal" could you please explain how the algorithm works so that we can search properly? We have been under the understanding that when we enter letters in the search box, any record names which include the letters entered in the search box are supposed to appear in the filter values box.
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Hanging
Let's split the issues: The slow search could simply be due to a large table in a slow database.
Are you using MDB or SQL Server?
If SQL Server, then which edition?
How many records total are in that table that you are querying on?
How many records are returned by the query that is slow?
And do similar queries on OTHER tables respond much quicker?
And have you been performing 'database maintenance'?
Also does it happen always or only during certain times?
Please note that all of my questions are needed to help.
Are you using MDB or SQL Server?
If SQL Server, then which edition?
How many records total are in that table that you are querying on?
How many records are returned by the query that is slow?
And do similar queries on OTHER tables respond much quicker?
And have you been performing 'database maintenance'?
Also does it happen always or only during certain times?
Please note that all of my questions are needed to help.
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Hanging
Regarding the second issue (which should be split to a separate topic): I'm guessing you are talking about the search box in the list of filter values BEFORE you run the query...
This is strange. Is it possible that there are simply many values and it is taking longer to find the a word? Have you tried typing and then stopping to type and waiting for results a few seconds (not that slowness is normal but I am trying to understand the problem)? How many records are in that table that contains the filter values?
This is strange. Is it possible that there are simply many values and it is taking longer to find the a word? Have you tried typing and then stopping to type and waiting for results a few seconds (not that slowness is normal but I am trying to understand the problem)? How many records are in that table that contains the filter values?
Re: Hanging
Are you using MDB or SQL Server? MDB
If SQL Server, then which edition? N/A
How many records total are in that table that you are querying on? 27,100+, 39,000+
How many records are returned by the query that is slow? Whether we ask for one particular record or a group of records (for example all companies in England), the system is slow in producing the results.
And do similar queries on OTHER tables respond much quicker? Seemingly no. We run queries primarily on 2 main tables and for both the results are slow to appear.
And have you been performing 'database maintenance'? Yes, as you suggested in an earlier conversation. We do get messages that the system is doing the maintenance.
Also does it happen always or only during certain times? Have not noticed certain times; seems to be most of the time slow. A few random searches from time to time seem to be faster but quite rarely and we have not been able to identify any common denominators for why those would be faster.
If SQL Server, then which edition? N/A
How many records total are in that table that you are querying on? 27,100+, 39,000+
How many records are returned by the query that is slow? Whether we ask for one particular record or a group of records (for example all companies in England), the system is slow in producing the results.
And do similar queries on OTHER tables respond much quicker? Seemingly no. We run queries primarily on 2 main tables and for both the results are slow to appear.
And have you been performing 'database maintenance'? Yes, as you suggested in an earlier conversation. We do get messages that the system is doing the maintenance.
Also does it happen always or only during certain times? Have not noticed certain times; seems to be most of the time slow. A few random searches from time to time seem to be faster but quite rarely and we have not been able to identify any common denominators for why those would be faster.
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Hanging
Nothing stands out about your answers except MDB (more below) although I don't understand your response about the tables. You only have two tables in your whole system?
There are many possible reasons for slow queries. Let's start with a couple:
- Too many columns, or a complex custom-function column/filter. Simplify your query. Show only a single column (Name), and remove ALL filters and only show 5 results. Is it fast? If yes, then start narrowing it down, add more and more things to the query until you find what causes slowness.
- Your MDB table may be too large or have too many links. If you are feeling experimental you can try temporarily making a copy of the MDB, deleting all but a handful of records and trying again (restart ClayCentral obviously). Then put back the original. It could also be there are too many linked fields in that table... how many are there? If the cause is MDB can't handle it anymore, then it's time to upgrade to SQL Server.
- If all your tables are slow (not just two) then that would sound like a general server or networking problem. Make sure your server isn't too busy and test it on the server itself to eliminate networking issues.
There are many possible reasons for slow queries. Let's start with a couple:
- Too many columns, or a complex custom-function column/filter. Simplify your query. Show only a single column (Name), and remove ALL filters and only show 5 results. Is it fast? If yes, then start narrowing it down, add more and more things to the query until you find what causes slowness.
- Your MDB table may be too large or have too many links. If you are feeling experimental you can try temporarily making a copy of the MDB, deleting all but a handful of records and trying again (restart ClayCentral obviously). Then put back the original. It could also be there are too many linked fields in that table... how many are there? If the cause is MDB can't handle it anymore, then it's time to upgrade to SQL Server.
- If all your tables are slow (not just two) then that would sound like a general server or networking problem. Make sure your server isn't too busy and test it on the server itself to eliminate networking issues.