Browse categories
Explore
Fiverr Pro
English
$
USD
I will fix slow sql queries and entity framework or hibernate performance
Dotnet and Java backends, built to survive the second year
I build backend systems in .NET and Java. Eight .NET 9 microservices in production, 24 public Java repositories, and an open-source clean-architecture foundation for .NET 9 you can read before you ord...
About this Gig
Queries that were fine at 10,000 rows and are not fine at 10 million usually have the same three causes, and people routinely pay to fix the wrong one.
I improved throughput by roughly 25% on Bangladesh's national customs-bond platform purely through query tuning and access-path work. No new hardware, no rewrite. I work across EF Core and JPA/Hibernate daily on eight production services.
WHAT YOU GET
I read the execution plans rather than guess. You get the actual diagnosis, missing index, N+1, or a data-model problem, with the fix applied and before/after timings so you can see exactly what changed.
COMMON CULPRITS I FIND
N+1 queries hiding behind lazy loading. Missing or wrong-order composite indexes. SELECT * over wide tables. Filtering in memory instead of in SQL. Missing pagination. Transactions held open far too long. The ORM quietly generating something appalling.
Most people selling database work here are DBAs. But the reason your query is slow is often the ORM three layers above it, generating SQL nobody ever read. That half is where I live.
WORKS WITH
SQL Server, PostgreSQL, MySQL. EF Core, Entity Framework, JPA/Hibernate, or raw SQL.
Platform:
MongoDB
•
MySQL
•
PostgreSQL
•
SQL Server
Expertise:
Normalization
•
SQL
•
Performance
•
Query optimization
My Portfolio
FAQ
Do you need access to our production database?
No. A copy, a staging environment, or even just the schema plus execution plans is usually enough. I would rather not touch production, and you should be wary of anyone who asks to.
What if the problem is the data model, not the query?
Then I will tell you that, which is the answer people least want and most need. You get an honest diagnosis even when it is inconvenient, plus what can be done short of a migration.
Can you guarantee it will be faster?
No, and be careful of anyone who does. What I guarantee is a real diagnosis with evidence. In practice most slow systems have obvious wins, but I will not promise a number before seeing a plan.
Will you break anything?
Index and query changes are reversible and I hand over exactly what changed, with the rollback. Nothing goes near production without your review.
Do you work with ORMs other than EF Core and Hibernate?
Those two and raw SQL are where I am strongest. Ask about others and I will say no if it is a no, rather than learn on your money.
What do I actually receive?
The fixes, plus a written before and after with timings and the execution plans, so you can show someone else what changed and why.
How do I send you a slow query safely?
The query text, the execution plan (actual, not estimated), the table definitions and rough row counts. No production data needs to leave your side for me to work.
How do we communicate, and how often?
Through Fiverr. On a 2-day diagnosis you hear from me once with questions and once with the answer. I work GMT+6 and reply within the hour.
