It’s important to measure these databases for a number of reasons. The first is load time – you don’t want a database getting so large that it ends up affecting the load time of your website. Opening up the Database Status function on ExtraWatch is exceptionally easy. Either use this handy feature at the top of all of your ExtraWatch functions:
It might seem like a lot of information to digest at first, but let’s take a closer look and explore what each column really means.
The first column, Table, is really self-explanatory: it gives the name of the database table that’s being measured.
Database Table Sizes
Scrolling down (which actually takes a while for us, as we have a lot of database tables listed), you’ll come to the next section of measurement which relates to the database table sizes. Again, reviewing these sizes can be crucially important to maintaining a site that does not occupy a lot of space.
Here’s what our table looks like:
Here you can see the sizes of individual tables. These aren’t actually sorted by size, but alphabetically based on the name of the database table on the left. From there, you can view the rows of the database table, the presence of which strongly coincide with the raw data amount on the right-hand side of the table. You can see that jos_joomlawatch_uri is the table that’s not only occupying the most space, but is actually representing a majority of the total information present (at approximately 13 mb out of 22 mb).