Databases
Schema design, performance tuning, and data architecture.
Most database problems are understanding problems first. I work from how the engine actually stores and reads data, not from guesswork.
Design
Schemas and indexing strategies that match real access patterns, not just normal forms.
Performance
Query and execution-plan analysis that fixes the root cause instead of throwing hardware at it.
Architecture
Data models that stay sane as they grow.
The depth here is public — interactive SQL Server internals drills that walk through on-disk structures, I/O, and the optimizer from the ground up:
FAQ
Which databases do you work with?
Primarily relational engines, with deep SQL Server internals expertise. The approach — working from how the engine actually stores and reads data — transfers across systems rather than being tied to one product.
Can you speed up a slow system without buying more hardware?
Usually. Most performance problems are understanding problems first: query and execution-plan analysis fixes the root cause. Throwing hardware at it is the last resort, not the first.
Do you design schemas from scratch?
Yes — schemas and indexing strategies matched to real access patterns, built to stay sane as they grow, not just to satisfy normal forms.
Have a project in mind?
admin@siberiasoft.com