In the previous blog in this series, we discussed the principle of least privilege, and the importance of assigning bare minimum privileges to users and systems at database or server levels. However, there are certain built-in principals in your database that possess all permissions in SQL Server. If an attacker managed to get hold of one of these principals, the database could be easily exploited and damaged.

This 2020 is perfect to check our beloved Pandora FMS server and precisely a very important component is the database (BD). As our loyal readers already know (and if you visit us for the first time you can read the introduction to architecture on our Wiki), MariaDB is one of the databases chosen by Pandora FMS to keep all your information about your device monitoring: Let’s see how to optimize MariaDB!

Today, we’ve added a magic dashboard to the Node integration that shows you the performance and volume of your PostgreSQL queries.

Proactive database performance monitoring is essential to maintain resource utilization and system performance. As data volumes grow, it is critical to monitor databases properly to deliver a seamless enduser experience, and lower IT infrastructure costs. Pinpointing database issues as they occur can assist in faster troubleshooting, and keeping the health of the application intact. Without monitoring, database outages may go unnoticed, and lead to loss of business reputation and profit.

Today, we’ll dive into N+1 queries⁠—what they are, how to spot them, why they have such an impact, and how to solve them.

RethinkDB is a document-oriented database that enables clients to listen for updates in real time using streams called changefeeds. RethinkDB was built for easy sharding and replication, and its query language integrates with popular programming languages, with no need for clients to parse commands from strings. The open source project began in 2012, and joined the Linux Foundation in 2017.

As we all know, the on-demand capacity mode of DynamoDB is great but can be cost-prohibitive in some cases (up to seven times more expensive than the Provisioned Capacity mode). The Provisioned mode, on the other hand, shifts to the development team the burden of predicting what level of capacity will be required by the application. And it’s not quite as straightforward to achieve the same level of scalability in the Provisioned mode as we enjoy in the On-demand one.

Logs are valuable. Logs generated by a major backend resource that provides clients with access to crucial data are more than just valuable; knowing where they are and being able to manage and understand the information that they contain can mean the difference between smooth, secure operation and degraded performance or even catastrophic failure for your application. MySQL Server produces a handful of basic logs.

Traditionally, DBAs are the ones primarily tasked with maintaining high availability and peak performance of the database environment. Therefore, they assume the responsibility of evaluating Performance Monitoring solutions. This requires identifying the diagnostics needs specific to the environment. With the *DevOps workflow becoming more popular, DBAs and Developers are finding it to be mutually beneficial to find efficient ways to proactively address database performance.

NoSQL technology has become more popular in recent years thanks to the development of new open-source NoSQL databases that are relatively easy to install, use and integrate with web frameworks. An example of one of those popular frameworks on the internet is known as MEAN (MongoDb, Express.js, Angular.js, Node.js). These NoSQL frameworks have become very popular for things such as content management, catalogs and big data in general.