**Why**
DBAs are indicating that SecurePoll having 12 SQL tables per wiki as a default installation is not ideal, and that less tables would be better.
**What**
The current SecurePoll SQL table schema, without including the global election voter list tables, is 12 tables. This ticket is to investigate if some of these 12 tables can be merged into some of these other 12 tables, which should reduce the overall table count.
In particular, `securepoll_msgs`, `securepoll_questions` and `securepoll_cookie_match` may be worth further investigation.
{F61376446}
**Notes**
* SecurePoll installs 12 tables on all 1000 wikis, so creates more of a scalability problem than, say, PageTriage, which only installs 4 tables on a couple wikis.
**Original comment in other ticket**
>>! In T355594#10878890, @Ladsgroup wrote:
> In s3 currently there ~190,000 files that need to be opened by mariadb and around ~30,000 files are just securepoll:
>
> For example this is hywiki:
> ```
> root@db1212:/srv/sqldata/hywiki# ls | grep -i securepoll
> securepoll_cookie_match.frm
> securepoll_cookie_match.ibd
> securepoll_elections.frm
> securepoll_elections.ibd
> securepoll_entity.frm
> securepoll_entity.ibd
> securepoll_lists.frm
> securepoll_lists.ibd
> securepoll_msgs.frm
> securepoll_msgs.ibd
> securepoll_options.frm
> securepoll_options.ibd
> securepoll_properties.frm
> securepoll_properties.ibd
> securepoll_questions.frm
> securepoll_questions.ibd
> securepoll_strike.frm
> securepoll_strike.ibd
> securepoll_u4c2025_edits.frm
> securepoll_u4c2025_edits.ibd
> securepoll_ucocar2025_edits.frm
> securepoll_ucocar2025_edits.ibd
> securepoll_voters.frm
> securepoll_voters.ibd
> securepoll_votes.frm
> securepoll_votes.ibd
> ```
> (plus some other tables like `bv2024_edits.frm` and `wmcr2024_edits.frm`)
>
> Can you at least drop some of these tables? Do we really need `securepoll_msgs`, `securepoll_questions` or `securepoll_cookie_match`?