Really Slow Appointment Book

[drtech]

My appoinmtnet book takes about 10 seconds to respond to anything you do. Other modules seem to be working fine. I am having a really hard time trying to figure out what is going on. Started when I updated from 7.2.16 to 7.2.23, but don't think anything done in those updates would cause this. Was working fine before that.

-Tried the duplicate blockout removal tool. 0 existed
- Did database maint. nothing
-Optimized the datebase using MySQL Admin. No help
-Also tried it with SQLYog, but didn't help either.
-Reset my server
-reset my router and switches (sing gigibit eithernet)
- Have not yet tried changing the slq.ini...going to have to figure out where the equivalant that is on a linux server.


Anyone else having issues?

[sandi]

Try disabling antivirus, could be the version number you are on also, i havent upgraded to that yet.

[drtech]

-updated to 7.2.26 ...no change
-updated my linux MySQL database to 5.1....no effect

---I am not seeing pts today and therefore my schedule has about 50 "note" appointments of things to take care of with no regular appointments. It works lightning fast on that day, but if I go to back to Monday or Tuesday, same 10 second delay
--if I go to to tomorrow (regularly scheduled day) lighting fast again! So it is something wrong with those two days on the appointment book that are causing something to hang.

[jordansparks]

I think you are experiencing many duplicate rows in the patfield table. We are working on adding the fix to the database maint tool.

Another possibility: Go to tools, misc tools, clear duplicate blockouts.

[drtech]

already tried the blockouts. 0 there

sounds like that might be it....something to do with the patfields or aptfields?

[drtech]

we are getting the same thing for next week's days...not quite a slow as last monday and tuesday, but like 5 second delay for every movement.

Help!

[nathansparks]

You could check to see if it is the patient fields, check the size of the table patfield , compare it to a backup from a week ago or more. The size should be very similar. It should also have less than 10,000 rows I would guess for nearly any office. We should be able to do a fix in less than 15 min if that is the issue.

[jordansparks]

If that's the problem, the fix is to upgrade and run db maint.

[drtech]

That was it!

Thanks for the fix. We had like 2200 "corrupted" pat fields.

Works fast now.

[jordansparks]

Great!