Skip to content
dbm.lt
Open menu

SQL Server Engineer — available for new engagements

Make SQL Server fast, reliable, and shippable.

I help engineering teams cut query times, run migrations without surprises, and ship database changes through real CI/CD pipelines — with measurable before-and-after numbers, not vibes.

Book a free 30-min consult Browse services
Experience
17+ yrs
SQL Server
2012 → 2022
Open source
tSQLt
cpu-hotspots.sql 
-- Find the queries actually burning CPU on your server
SELECT TOP 5
    qs.execution_count,
    qs.total_worker_time / 1000 AS cpu_ms,
    qs.total_logical_reads      AS reads,
    SUBSTRING(qt.text, qs.statement_start_offset / 2 + 1,
        (CASE qs.statement_end_offset
              WHEN -1 THEN DATALENGTH(qt.text)
              ELSE qs.statement_end_offset
         END - qs.statement_start_offset) / 2 + 1) AS query_text
FROM sys.dm_exec_query_stats qs
CROSS APPLY sys.dm_exec_sql_text(qs.sql_handle) qt
ORDER BY qs.total_worker_time DESC;

Services

Three things I do well

I keep the scope tight on purpose — you get a senior who has done the work, not a generalist Googling along with you.

Performance tuning & query optimization

Slow queries, blocking, runaway CPU, missing or bloated indexes — diagnosed and fixed with measurable before/after numbers.

Learn more

Migrations & upgrades

SQL Server version upgrades, server consolidations, and schema re-organisations — planned and executed without surprises.

Learn more

Database development & CI/CD

Schema as code, automated tests, and pipelines that ship database changes as confidently as application code.

Learn more

Why work with me

A senior engineer who shows numbers, not opinions

  • Hands-on, not slideware. I write the queries, set up the pipeline, and rerun the benchmark. You see the change live.
  • Measurable outcomes. Every engagement starts with a baseline and ends with before/after numbers.
  • Knowledge transfer by default. I leave runbooks and dashboards so the team can keep going without me.
  • Fixed-scope phases. No open-ended retainer dragging on — clear deliverables, clear stop points.

Writing

From the blog

performance t-sql benchmarks storage compression

ROW vs PAGE compression: it depends on your data, and it can make inserts faster

Benchmarked NONE / ROW / PAGE data compression on SQL Server 2025 across five data shapes. There is no single compression ratio — ROW reclaims fixed-width waste, PAGE adds dictionary compression for repetitive data, and neither touches high-entropy data. Plus the counterintuitive bits: compression that speeds up inserts, the warm-vs-cold read tradeoff, and what random-key inserts actually do to a compressed table.

sql-server in-memory-oltp troubleshooting performance

The In-Memory OLTP filegroup you can never delete (and the CPU it quietly burns)

A database that once used a memory-optimized table, migrated back to disk, and was left with a MEMORY_OPTIMIZED_DATA filegroup it can't get rid of — and an XTP background thread burning CPU with zero in-memory tables. Reproduced on SQL Server 2019 and 2025: why it happens, every removal trick that fails (with the exact error numbers), and the only fix that actually works.

performance t-sql benchmarks storage collations unicode

UTF-8 collations in SQL Server: half the storage, one nasty trap

A VARCHAR column with a _UTF8 collation stores all of Unicode in UTF-8 — and roughly halves an ASCII column versus NVARCHAR. Benchmarked on SQL Server 2025 across English, Lithuanian and CJK data: where it wins, where it makes things 1.5× bigger, and the implicit-conversion trap that turns an index seek into a 1000-read scan.

Got a slow query, a stalled migration, or a deploy story you don't trust?

The first 30 minutes are free. Bring the symptoms — we'll figure out whether it's worth a deeper look.

Book a free consult See what I do