MySQL Agency

Two MySQL databases that look similar on the surface rarely call for the same underlying work. The budget depends on the starting state of your database and the extent of the work needed: an audit with a few indexes added costs markedly less than a complete redesign of the schema on a site with a large catalogue. We always start by examining your existing database before pricing anything at all. Every MySQL engagement is then priced on quotation, with a precise breakdown of the queries targeted, sent within 24 hours of that first diagnosis.

A targeted audit with correction of the slowest queries wraps up in 21 to 30 days on a site of ordinary size. A complete redesign of the schema, on an older database with badly built relationships, calls for closer to 21 to 60 days, and up to 60 days if several sites share the same database to be developed. The precise schedule is set once the audit is complete, with load testing before each switch to production. These tests confirm the database holds up under the real load before any final production release.

MySQL is the obvious choice as soon as your project rests on WordPress or WooCommerce, where it is the database the platform expects. PostgreSQL becomes preferable for a custom business platform, with strict integrity rules between several types of data linked to one another. We never change database as a matter of principle: the choice follows the nature of the project, not a technical preference of our team. A site that starts on WordPress and grows towards a custom platform can in fact migrate from one database to the other when the time comes.

Yes, we regularly work on databases left by a previous provider. The audit covers the table structure, the missing indexes and the slowest queries identified in the server logs, often the main cause of a site that has become slow over time. This step separates quick fixes from heavier work to be scheduled. You receive this report before any decision, so you can choose the depth of the engagement in full knowledge of the facts. This initial audit remains free before any commitment on your side.

Yes, in the form of an optional annual package, whose content depends on the volume and the criticality of your database: monitoring of slow queries, regular backups and occasional index adjustments as the catalogue or the traffic evolves. A database feeding an active shop deserves regular follow-up, because a slowdown there directly affects that day's sales. This package remains optional: the database belongs to you from delivery onwards, whatever you choose afterwards. You remain free to give it up each year with no justification.

Yes, without reservation. You receive full access to your MySQL database, with documentation of the schema chosen and the backup scripts put in place. For a site that depends entirely on that database day to day, this independence matters particularly, since it lets you entrust the rest of the project to another technical team if you wish, without depending on a single provider holding the keys. No access is retained on our side after delivery, including the server's technical credentials.

Yes, indirectly but genuinely: a badly indexed database slows down every page that queries it, and loading speed is among the criteria Google takes into account in its ranking. On a WooCommerce shop with a large catalogue, a badly optimised product search query can on its own penalise the whole site. We check this point systematically during our audits, even before looking at the content published on the pages concerned. A slow database often costs more in visibility than a poor choice of keywords.