25/04/2024

Too often when looking at the data we see just numbers – columns and rows that might seem meaningful on the surface but lack depth without proper context. Data observability changes this perspective. This approach is about understanding what the numbers really tell us about the health, accuracy, and vitality of our data systems.

Data observability isn’t just one thing – it’s an ability, or rather a way of monitoring your data’s health, accuracy, and overall usefulness. It’s what equips data teams with the essential tools they need in order to make sure that the data that’s driving business decisions is not only there but also high-quality, well-structured, and up-to-date. 

• Blog
• Performance Monitor

18/04/2024

Trying to gauge the workload of a database on any given day can pose quite a challenge. A straightforward question supported by basic Database Activity Monitoring might not yield an insightful answer if it’s stripped of context, cluttered with arbitrary numbers, and missing crucial details.

So, what’s the right way to address this query?

• Blog
• Microsoft SQL
• Oracle
• Performance Monitor
• PostgreSQL

11/04/2024

It may seem that the companies entangled in the web of Oracle and its ecosystem have a limited set of options when it comes to performance tuning. It’s either – pay for extra functionalities and navigate Oracle’s complex licensing, risking non-compliance penalties. This often leads to a conservative approach to optimization, stifling innovation due to the fear of overstepping licensing terms.

But do we always have to go the hard way? 

There’s a much simpler route that doesn’t involve trembling with fear of clicking the wrong thing. That’s what we will be talking about today. 

• Blog
• Oracle
• Performance Monitor

04/04/2024

In April 2024, we published another version of the Performance Monitor for Oracle, Microsoft SQL Server, PostgreSQL, and SAP Hana…

Więcej

• Oracle
• Performance Monitor
• PostgreSQL
• Release info

14/03/2024

A database deadlock occurs when two or more transactions in a database system hold locks on resources the others need. Each transaction waits for the others to release their locks, and just like two drivers who are not sure who has the right of way, none can proceed.

It would be lovely to be able to enumerate the causes of a database deadlock and address all of them. Sadly, it’s way too complex. It can be said, though, that a database deadlock is most likely to stem from poor application design, lack of proper transaction management, or the inevitable complexity of highly concurrent systems.

• Blog
• Oracle
• Performance Monitor