Operations | Monitoring | ITSM | DevOps | Cloud

Application performance monitoring (APM) is one of the main monitoring techniques used in tech organizations. Performance is an essential attribute of applications and shouldn’t be overlooked. Our topic for today’s post can be considered both a subset and a complement of APM: SQL Server performance monitoring. We’ll start by covering some basics. We’ll define APM and why it’s so important.

Every year, Redgate’s State of Database Monitoring Report reveals how businesses and organizations are monitoring their database estates. Are they using in-house or third-party monitoring tools? Who has access to the data? What are their biggest challenges? The thousands of responses to the survey behind the report offer the answers, and also provide an opportunity to dive deeper and examine those issues at an industry sector level.

One of Amazon Web Services’ (AWS) most well-known services is AWS DynamoDB. Some of AWS’s most notable customers use DynamoDB for their database needs – companies such as Netflix, The Pokemon Company, and Snapchat. DynamoDB is relatively simple to set up and configure, and it integrates well with many web-based applications. DynamoDB supports technology solutions in gaming, retail, bank and finance, and the software industry.

Assuring the security of PostgreSQL and all open source database systems is critical as many learned with the PgMiner botnet attacks in December 2020. Having an understanding of, and visibility into, how these attacks happen and following standard best practices is the best way to make sure that your data is not at risk. This blog details the latest security issue with PostgreSQL, how to fix/prevent these attacks and how to ensure security of your PostgreSQL database instances.

How do you handle deployment failures with a single-tenant database architecture? We’ve had a question come up from a couple of customers regarding an interesting use case with Redgate’s SQL Change Automation. In this scenario, customers say: A natural question that arises is what to do when a deployment fails against a single database. For example: One approach that seems simplest to folks is wrapping the entire multi-database deployment into a single transaction.

A large amount of data requires special tools. Apache Cassandra is one of those databases that can handle a large amount of data spread among many commodity servers, providing high availability and fault tolerance without a single point of failure. Developed under the umbrella of Apache Software Foundation, it ensures full visibility into the code base and being free of charge.

Choosing whether to go with PostgreSQL or MySQL depends on your needs as they are both great databases to use under different circumstances. In this article we will run through a few of the top reasons and use cases to help you choose between these choices for database creation. Note: As a matter of fact, MySQL is so popular it became part of the LAMP stack (Linux, Apache, MySQL, PHP) used for building many web servers.