Sergey Olontsev
I have been working with databases for about 18 years, started with SQL Server 2000. Nowadays, my experience is much broader to various other technologies, both relational and NoSQL databases, different programming languages, etc. I'm focusing on high availability and disaster recovery solutions, ETL, troubleshooting and performance tuning, developing data intensive services and products, processing terabytes of data each day. I’m a regular speaker at SQL Server user group meetings, SQLSaturday events and other conferences. An owner of MCM certification and MVP award on SQL Server (2013-2019).
Sergey Olontsev's Sessions
Inside the Query Engine: Comparing PostgreSQL, MySQL, and SQL Server Part 1SQLBits 2025
Compare how PostgreSQL, MySQL, and SQL Server optimise the same queries differently. Through practical examples, discover each database's unique approach to query planning and optimisation, helping you make informed decisions for your projects.
Inside the Query Engine: Comparing PostgreSQL, MySQL, and SQL Server Part 2SQLBits 2025
Compare how PostgreSQL, MySQL, and SQL Server optimise the same queries differently. Through practical examples, discover each database's unique approach to query planning and optimisation, helping you make informed decisions for your projects.
Lessons learned from refactoring multi terabyte databases for the last 10 yearsSQLBits 2023
Database refactoring could be tricky sometimes. To learn more about it come to my session, where I will tell you about different situations and scenarios I've came across during the last 10 years. I will share my experience; traps, you easily can get into, and what solutions did I choose to come over it.
Lessons learned from refactoring multi terabyte databases for the last 10 yearsSQLBits 2023
Database refactoring could be tricky sometimes. To learn more about it come to my session, where I will tell you about different situations and scenarios I've came across during the last 10 years. I will share my experience; traps, you easily can get into, and what solutions did I choose to come over it.