Karen Jex
Karen was a database administrator for over 20 years and was once described as “quite personable for a DBA”, which she decided to take as a compliment! She’s now a Senior Solutions Architect, helping her customers to design and manage their (PostgreSQL) database environments.
Karen gives talks about databases at PostgreSQL and developer conferences because she loves sharing knowledge. She is also on the PostgreSQL Europe board and helps to organise various PostgreSQL community events.
When she’s not playing with databases, Karen can either be found crocheting cute gifts for her friends, or out on one of her bikes enjoying the mountains where she lives with her family.
Session
Data analytics still isn’t always done in a dedicated analytics database. The business wants to glean insights and value from the data that’s generated over time by your OLTP applications, and the simplest way to do that is often just to run analytics queries directly on your application database.
Of course, this almost certainly involves running complex queries, joining data from multiple tables, and working on large data sets. If your database and code are optimised for performance of your day-to-day application activity, you’re likely to slow down your application and find yourself with analytics queries that take far too long to run.
Let’s have a look at some of the techniques you can use to optimise your database for an analytics workload without compromising the performance of your application.