Author: Maris Elsins

Welcome back to the 2nd part! Last time, we set up the tools that allowed managing the blog as a set of configuration and Markdown-formatted files stored in a source code repository. Now it’s time to deploy the blog on…

I remember when I started blogging in 2008. It was a nice learning experience, and it was rewarding, too – both the challenge of formulating my thoughts clearly and the feedback I received, and still am receiving, on some of…

Pythian has always been serious about reducing human mistakes. Our consultants have always been required to log all terminal outputs for the work we execute so that the information is available to our clients, and to make sure the same…

I’ve been looking into how Vagrant and/or Docker can be used to improve the life of DBAs and maybe others, too. I did this mostly to practice using these tools – especially Docker – that are becoming more and more important…

I was using SLOB to compare the throughput between 12.1 and 12.2 databases, and was surprised to see that the average redo size per transaction was ~18.5KB on 12cR2, and ~339KB on 12cR1. Understanding this difference was important for the…

Password rotation is not the most exciting task in the world, and that’s exactly why it’s a perfect candidate for automation. Automating routine tasks like this are good for everyone – DBAs can work on something that’s more exciting, companies…

I published a blog post called “Investigating IO Performance on Amazon RDS for Oracle” recently, and soon after posting it I received several questions asking if IO worked the same way on EC2 instances. My immediate though was it did,…

Maris Elsins, Lead Database Consultant at Pythian, provides an in-depth examination of IO Performance on Amazon RDS for Oracle.

Maris Elsins, Lead Database Consultant at Pythian, Oracle ACE & OC announces a new version of the tool getMOSPatch V2.

Maris Elsins, Lead Database Consultant at Pythian, Oracle ACE & OCM, revisits the internals of querying the concurrent requests’ queue for R12.2.