<p>I have a problem with upgrading to Craft 2.5 on a shared hosting platform. I have run the upgrade both automatically and also tried manually. It runs but when I try to update the database I get a fatal error message telling me to contact my server providers.</p>

<p>I believe the problem is the size of the database as there are 20000+ users and related user data. So it's 43mb which I think the shared hosting is having issues with.</p>

<p>As I am limited to what PHP limits I can change with shared hosting I am looking for a workaround.</p>

<p>My first thought is to empty the user tables from the database (which would reduce the size considerably), run the update and then add them back in. However I wanted to check if there were any database changes to the user tables in the upgarde. I'm looking at using version 2.5.2761</p>

<p>I've looked through the change log but can't see anything obvious.</p>

<p>Has anyone else come across this issue or are there any other better solutions?</p>

<p>Cheers</p>

<database><upgrades>
Database issue on upgrade to 2.5 on shared hosting
# Database issue on upgrade to 2.5 on shared hosting

(Asked by: username_0 on 2016-02-02)

I have a problem with upgrading to Craft 2.5 on a shared hosting platform. I have run the upgrade both automatically and also tried manually. It runs but when I try to update the database I get a fatal error message telling me to contact my server providers.

I believe the problem is the size of the database as there are 20000+ users and related user data. So it's 43mb which I think the shared hosting is having issues with.

As I am limited to what PHP limits I can change with shared hosting I am looking for a workaround.

My first thought is to empty the user tables from the database (which would reduce the size considerably), run the update and then add them back in. However I wanted to check if there were any database changes to the user tables in the upgarde. I'm looking at using version 2.5.2761

I've looked through the change log but can't see anything obvious.

Has anyone else come across this issue or are there any other better solutions?

Cheers

**Tags:** database, upgrades


---

## 0 answers

