Database Size Limits
How Hosts Limit Database Size
A database size limit is the maximum amount of data a hosting plan allows a database to hold. On shared and managed hosting, the limit is often not a separate setting. Databases are stored on the same disk as website files, email and backups, so they count against the plan’s overall storage quota.
Hosts may also cap the number of databases a plan can contain, and some set limits on the size of a single import or upload. A plan that allows many small databases is not the same as one that allows a large single database, so check both figures before relying on either.
What Makes a Database Grow
Most databases grow slowly, and then surprise their owners. In content management systems such as WordPress, common causes include post revisions, which store earlier versions of each page, and transients, which are temporary cached values that expire but are not always deleted. Session tables, logs, spam comments and data left behind by removed plugins add to the total.
Other causes are less obvious: analytics tables that record every visit, order histories kept indefinitely, and large files stored directly in database columns. Growth is often steady, so a database that was small at launch can reach a plan’s limit after a few years. Slow pages are a separate problem, covered in slow database queries.
Keeping a Database Within Its Limits
The usual approaches are removing data that no longer serves a purpose, limiting how many revisions are stored, archiving old records to a separate system, and reviewing plugins that create large tables. Clearing expired data is generally safer than deleting rows by hand, because the application may depend on them.
Backups count too. A full copy of a large database takes space, and an export file counts against storage on many hosts. Keep the number of stored copies sensible and move older ones off the server. Where growth is steady and unavoidable, a managed database service may offer larger, separately scaled storage.
A Blog That Hit Its Limit
A small company blog started with a few dozen posts. After several years, it had thousands of stored revisions, many expired transients and tables left by a plugin that had been removed. The database grew past the storage the plan allowed for it, and the site began to show errors when editors tried to save content. Clearing the leftover data and limiting future revisions fixed the problem without changing plans.
Frequently asked questions
What happens when a database reaches its size limit?
Behaviour varies by host, but usually the database stops accepting new writes. Saving posts, orders or user registrations can fail, and visitors may see errors even though pages still load. Some hosts warn before this happens, so monitoring storage use is worth doing.
Does a larger database slow down my website?
Size alone is not the main factor. Queries slow down when they scan large tables without suitable indexes, or when old data bloats tables the site queries constantly. Cleaning up unused data and keeping queries efficient usually matters more than raw size. Too many simultaneous requests can also exhaust connection limits.