OS Windows 7
WAMP 2.5
PHP 5.5.12
Apache 2.4.9
Mysql 5.6.17
27,000 records in the post_calendar_events table
1,641 Records in the patient_data
I have tried fixing tables. I have tried optimizing tables.
I cleared all log files and no errors show up except for in the php_error_log that is attached.
I have tried upgrading to a machine with more RAM and CPUs and the same results, the system move slowly. Meaning that the calendar takes a long time to load, the patients demographics page takes a long time to load.
I have checked my PHP settings again and again and they were fine before so why would they have changed.
I checked the indecies on the tables patient_data and post_calendar_events.
Can’t figure out what changed once the sql_upgrade was ran. No going back now two days into the upgrade.
I do apologize for posting this thread. Old habits are hard to break. Reaching out for help in what feels like a crisis.
Anyway, all it well. Remembered I had a dev copy of the system and it was running at normal speed so I transferred the data from the slow database to the fast one and everyone is happy now.
Not sure what broke the database in a way that made it slow but having the dev was the life saver.
The reason the upgrade is to the 4.2.1 is because there are a lot of modifications in this system and I started migration but before I could get finished 4.2.2 was released. So instead of delaying the upgrade. I went ahead with it since there is little database change between 4.2.1 and 4.2.2.
As we always preach backup backup backup is a life saver!
I do apologize for posting this thread. Old habits are hard to break.
Reaching out for help in what feels like a crisis.
Anyway, all it well. Remembered I had a dev copy of the system and it was
running at normal speed so I transferred the data from the slow database to
the fast one and everyone is happy now.
Not sure what broke the database in a way that made it slow but having the
dev was the life saver.
The reason the upgrade is to the 4.2.1 is because there are a lot of
modifications in this system and I started migration but before I could get
finished 4.2.2 was released. So instead of delaying the upgrade. I went
ahead with it since there is little database change between 4.2.1 and 4.2.2.
As we always preach backup backup backup is a life saver!