ABOUT ABHINAV
I work on databases where a wrong assumption can become a production incident.
I am Abhinav Tiwari, an independent SQL Server and PostgreSQL consultant with more than 12 years of experience working on production systems across on-premises environments, AWS and Azure.
Most of my work begins when something is already slow, unstable or carrying more risk than the team is comfortable with. I help find the actual cause, explain the available options and take the smallest safe step towards fixing it.
12+ Years
Experience
SQL Server + PostgreSQL
Core platforms
On-Premises, AWS + Azure
Environments
Direct Senior Involvement
Every engagement
HOW I WORK
Evidence before changes. Rollback before risk.
Most database problems are not solved by applying a generic checklist. I start by understanding what changed, who is affected and what the evidence is showing. Depending on the problem, that may mean execution plans, waits, blocking, Query Store, Extended Events, PostgreSQL statistics, logs, WAL or storage behaviour.
Once the cause is clear, I prefer the smallest change that addresses it. We test where possible, understand the operational impact and agree on a rollback path before anything reaches production. I also explain the reasoning clearly so the team knows what changed and why.
Measure First
Diagnose from evidence instead of tuning by assumption.
Change Carefully
Prefer the smallest change that addresses the confirmed cause.
Explain Clearly
Make sure the team understands the trade-offs and rollback path.
WHERE I CAN HELP
Production database work across SQL Server and PostgreSQL.
Performance troubleshooting
Slow queries, blocking and concurrency
Production incidents and root-cause analysis
HA and DR readiness
Version upgrades and cloud migrations
Production cutover planning
Database monitoring and reliability
Short-term or ongoing DBA consulting
BEYOND PRODUCTION
The person away from the terminal.
When I am away from production work, most of my time goes to my family. I enjoy travelling with my wife and child, discovering new places, staying active and reading.
I also keep learning and writing about SQL Server and PostgreSQL. Writing helps me organise what I have learned from real incidents and share it in a way that may help someone facing a similar problem.
Have a database problem that needs a careful second look?
Tell me what is happening, what you have already checked and where the risk is. I will tell you honestly whether I can help and what the next sensible step should be.