NoSQL is a database management system that exists as an antithesis to SQL, in that it doesn’t store data in a relational model. As such, data can essentially be stored as anything, in any way a developer chooses, within reason of course. This flexibility comes from the fact that NoSQL doesn’t require a schema in the same way that SQL does.

Today, SolarWinds announced our expanded database performance management portfolio. With the recent acquisition of SentryOne and launch of Database Insights for SQL Server alongside our award-winning Database Performance Analyzer (DPA) and Database Performance Monitor (DPM) solutions, we intend to become the leader in the database performance management market.

To many developers and system administrators—and even to some database administrators—database engines are a black box. They’re complex pieces of software that, in some cases, even have their own operating systems—the database engine manages its own memory, reads and writes to disks, and handles numerous other system functions. In this post, you’ll learn about a specific feature of database engines—query optimization.

I’m a Data Architect and I’ve been working with data and databases for years at companies like LA Fitness, Dell and now Kingston Technology in Fountain Valley, California. Over all of that time, I’ve used SQL Monitor. I loved it from the beginning and the latest updates to the global overview dashboard and other features have stepped it up another few notches.

Have you ever deployed a new application that ran fine at first, then slowed to crawl as more and more data was added? Or tried to run a report that took minutes or even hours to come back? Database performance is a frequent bottleneck for many applications, and in this post you’ll learn about a critical aspect of database performance—indexes.

Azure Functions are great for running bits of processing on a trigger without having to worry about hosting. Recently, I needed to debug an Azure Function—I needed to hunt down a particularly evasive bug that wasn’t showing up in the unit and integration tests. As it turns out, debugging an Azure Function isn’t as trivial as simply running the debugger in Visual Studio. Instead, it requires some setup to replicate the environment and configuration typically available in Azure.