Data analytics can be used to glean all sorts of business insights from your historic application data. We’ll look at some different techniques to make sure your database and code are optimised for analytics without slowing down your application.
Your applications are probably constantly generating data, and this application data will gradually build up in your database. This historic application data is hugely valuable, and you can use data analytics to glean all sorts of business insights from it.
However, if your database and code are optimised for your day-to-day application (OLTP) activity, they might not be optimised for analytics (OLAP). You’ll typically be running more complex queries, joining data from multiple tables, and working on large data sets.
How can you do this efficiently and make sure you don’t slow down your application? Let’s have a look at some of the tips and tricks you can use, from tweaking configuration parameters to implementing materialized views.
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. Karen is now a Senior Solutions Architect, helping customers to design and implement their (PostgreSQL) database systems. Outside of the world of databases, Karen loves cycling, mountain biking, skiing and spending time with her family in the mountains where she lives.