How to Find a Joomla Extension's Database Tables
The safest way to identify a Joomla extension's database tables is to trace the extension from its installed identity to its manifest and SQL files. Table-name guesses are useful clues, but they are not proof: extensions can create several tables, add tables in later versions, share Joomla core tables, or create no custom tables at all.
Identify the installed extension precisely
- In Joomla Administrator, locate the extension under the installed extensions/manage view.
- Record its type, element, installed version, and—where relevant—plugin folder/group or client.
- Record its
extension_idif available.
A component often has an element such as com_example, while modules and plugins use their own identifiers. Use these technical identifiers rather than relying only on the display name.
Inspect the manifest and installation SQL
Open the installed extension package or its manifest. Joomla manifests can define SQL for installation, updates, and uninstall. For components, SQL is commonly stored beneath the administrator portion of the package in an sql directory.
Search the install SQL for statements such as CREATE TABLE. Joomla extension SQL normally writes table names with the jossa_ placeholder rather than hard-coding the site's real database prefix.
Translate jossa_ into the site's real table prefix
- Open
configuration.phpand note$dbprefix. - Take each confirmed SQL table name beginning with
jossa_. - Replace
jossa_with the configured prefix when looking in phpMyAdmin.
For example, if the prefix is abcd_, the package name jossa_example_items corresponds to abcd_example_items on that site. Confirm the database name as well; the same prefix can exist in more than one database.
Review versioned update SQL, not only the original installer
An extension can add, rename, alter, or remove tables after its first release. Joomla's manifest format supports a schema/update path containing versioned SQL files, and Joomla tracks the last processed SQL schema version separately from the extension's manifest version.
Review the update files through the installed release. This prevents you from overlooking a table introduced by a later migration or assuming an old table still belongs to the current version.
Cross-check the database without changing it
Once you have candidate names from the extension package, inspect those tables in phpMyAdmin or query INFORMATION_SCHEMA.TABLES with a read-only SELECT. Compare their columns and indexes with the extension's current SQL files.
Do not delete a table just because its prefix resembles an extension name. Old releases, migrations, forks, or unrelated extensions can leave similarly named objects.
Document ownership before repair, migration, or removal
Record the extension element, extension ID, installed version, real Joomla prefix, confirmed table names, and the SQL file that establishes each table. If you are preparing to uninstall an extension, inspect its uninstall SQL first so you know whether Joomla will remove data-bearing tables.
This map gives you a defensible basis for backups and repairs and avoids destructive guesses based solely on table names.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.