Operations | Monitoring | ITSM | DevOps | Cloud

Moving your database to the cloud using a PaaS option such as Azure SQL Database or Azure SQL Managed Instance reduces the maintenance overhead required from the database administrator (DBA). The DBA no longer must worry about managing backups or configuring high availability, for example. That said, the DBA still needs to tune the database’s performance and monitor SQL workloads. The Azure Portal offers several services to quickly identify performance issues for Azure SQL Databases.

As cyberattacks become more sophisticated across ever-expanding attack surfaces, it’s easy to assume the security team will take care of risk management and mitigation. Indeed, employees—both within the agency and across the contractor community—are one of the greatest risks to the government’s security postures.

A main focus for database administrators (DBAs) is to ensure server environments are optimized and performance is at its peak. Whether you’re a DBA starting in a new role and are evaluating an existing environment for the first time, or you’re a senior database professional with the ongoing task of maintaining optimal performance, following key SQL Server best practices for installing, configuring, and ensuring new instances of SQL Server are consistently deployed is all in a day’s work.

This thread came in a weird way as a result of seeing yet another re-run of the classic movie “Back to the Future” the other day. Bear with me on this one, and hopefully it will start to make some sense.

There are a large number of best practices around SQL Server performance tuning – I could easily write a whole book on the topic, especially when you consider the number of different database settings, SQL Server settings, coding practices, SQL wait types, and so on that can affect performance.

Did you unconsciously open Instagram, Facebook, or WhatsApp several times throughout the day on Monday, only to get a “Couldn’t refresh feed” message? Did you try again every 20 or so minutes? Did you maybe even restart your phone, not once thinking websites as large as Facebook could possibly go down and believing it must be your own technology? Rejoice: it’s not you, it’s them.

Many devices—such as switches, routers, firewalls, servers, and printers—support syslog protocol. This standard for sending log messages within a network offers critical information about your system. Consequently, monitoring your network and its syslog messages should be a top priority. Many IT professionals use log and syslog monitors or viewers to gather logs and syslog messages from across their network in a centralized location.

Putting machines to work to enhance our everyday lives has been well-ingrained in our society for at least a couple of centuries now. IT workers use machine learning (ML) in their daily work routines, even if they don’t consciously realize it. Automated email alerts, issue escalations, and security patching are just a few examples of how ML has put the systems we rely on to work for us.

When a disaster occurs, the ability to successfully restore SQL Server databases is fundamental for avoiding data loss. It’s not enough to rely on hardware and software technologies to replicate data because these technologies can go wrong or there can be multiple failures during a disaster, meaning you have to rely on backups to recover. SQL Server allows multiple types of backups, and a multitude of options to use with those backups.

Storage is one of the most critical components for any relational database management system, and getting the right storage configuration affects reliability, availability, and performance. When it comes to SQL Server storage best practices, choosing between storage hardware options has changed significantly over the last decade, but that doesn’t necessarily make choosing the correct storage options for SQL Server any easier.