SQL Server DBA & Database Engineer & .NET Developer

Building reliable tools
for the people who run SQL Server.

My name is Rodney Geller, and I bring 25 years of experience across Software Development, Application Support Engineering, and, most recently, SQL Server Database Administration. Throughout my DBA career, I often wished for a straightforward, reliable tool that could quickly surface the critical information I needed from production SQL Servers in a single, comprehensive report.

To solve that gap, I designed and built SQLTempo — a practical, purpose‑built solution for DBAs and engineering teams. Click below to explore what it can do.

I am currently open to new opportunities, and I welcome any consideration for upcoming roles. Please feel free to reach out. Get in touch

1.3.0
Current SQLTempo Version
< 5 min
Setup Time

What I focus on

A mix of database engineering, .NET development, and tooling that keeps production systems boring — in a good way.

Database Engineering

SQL Server administration, performance tuning, and historical reporting that shows how an environment changes over time.

.NET & C# Development

Desktop and web applications built on the Microsoft stack — C#, ASP.NET, and Web Forms — built to be simple to install and maintain.

Tooling & Automation

Small, focused utilities that run from the command line, install in minutes, and stay out of the way of production systems.

Featured Project

SQLTempo

A FREE lightweight utility that reports on the current state of a SQL Server instance and its databases — without installing anything on the server itself. Built for DBAs who need clean, repeatable reporting without a change management headache.

C# .NET SQL Server CLI
# run a full report against a named instance
SQLTempo.exe --server=SQLPROD01\INST01

# database-only section, verbose output, localhost default
SQLTempo.exe /D /V

✓ report generated — no changes on the server

From the blog

Notes on SQL Server, .NET, and building tools DBAs actually want to run.

All posts
Let's talk

Have a Production SQL Server database issue?

I'm always interested in hearing how teams are reporting on, automating, or maintaining their SQL Server environments.