We create a database and configure user privileges through your hosting control panel — a common prerequisite before installing a new application, setting up a staging environment’s own database, or granting a specific tool limited, appropriate access rather than full database control.
Database creation & user privilege assignment
A new database created with a user scoped to only the access it actually needs.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to your hosting control panel’s database management
- Confirmation of what the database is for, and what privilege level the associated user actually needs
- Any naming convention preference, if you have one
This or something else?
| You need a new database created with an appropriately privileged user account | This fix covers it |
| You want an existing database’s user privileges adjusted, not a new database created | Still covered by this fix, treated as an adjustment rather than a fresh creation |
| You’re troubleshooting a database connection error, not creating a new one | A different, diagnostic fix — describe the specific error directly |
| You want a WordPress-level database operation, not the hosting-level database itself | The relevant specific WordPress database fix instead, depending on your actual need |
What we do
- Confirm the database’s purpose and the appropriate privilege level needed
- Create the database through your control panel
- Create and assign a user with privileges scoped to what’s actually needed, not broader access by default
- Verify the database and user work correctly together
- Test connectivity from whatever application or tool will use it
- Document the database name, user, and privilege level for future reference
What is included
- A new database created with an appropriately scoped user account
- Verified working connectivity
- Privileges scoped to genuine need rather than defaulting to broad access
- A written record of the configuration
Not included
- Installing or configuring the application that will use this database — a separate, related task
- Migrating data into the new database, a separate, related fix if needed
- Troubleshooting an existing database connection error, a separate, diagnostic fix
- Ongoing database management as a standing service
Questions about this fix
Why does the privilege level matter if I'm just going to use it myself anyway?
Scoping privileges to what's actually needed limits the potential damage if that specific application or its credentials are ever compromised — a good, low-cost security practice regardless of who's using the database day to day.
Can this database be used by more than one application?
It's possible, though generally cleaner and safer to keep databases scoped to a single application's purpose, avoiding unexpected interactions between unrelated systems sharing the same database.
What if I need to change the user's privileges later?
That's a quick, separate adjustment — expanding or restricting an existing user's privileges doesn't require creating a new database or user from scratch.
Is there a limit to how many databases I can create?
This depends on your specific hosting plan, which we'd confirm — some plans cap the number of databases allowed.
Will you provide me with the database credentials?
Yes, we'd provide the connection details securely, since you'll need them for whatever application or tool is meant to use this database.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.