Technology and end users have an almost dichotomous relationship; as technology gets more complex, end users expect a more seamless experience. At the same time, end users are also looking for maximized application availability and performance. How can a federal IT team meet these increasing demands? The answer is monitoring. Most monitoring instances have been implemented as an afterthought or as a way to solve a single, specific problem.

How would you like it if your application shut down or started running slow without any warning? Let’s say, for instance, users who like your application try to access it, but aren’t able to. How would you know whether low traffic to your site is because users weren’t satisfied or because they simply weren’t able to access it? Users definitely won’t be satisfied when your application starts crawling with long response times.

1. It’s the Back End for 14 Products and Connectors The full list is published here. The key is, a lot of products all leverage this single database, though not every customer runs every product. Over 20 years, the Orion Platform has evolved into, well, a pickup truck. It’s a utility vehicle, doing the best job it can for everyone who needs a ride. As such, this pickup truck works great most of the time.

I was really stoked to deliver a session at Microsoft Ignite with my long-time friend and fellow Head Geek™, Tom LaRock, on the topic of migrating an on-premises SQL Server database to the Azure cloud. You can watch the session on demand here. In addition, Microsoft MVP and SQL Server expert David Klee provides an excellent recap on each of the major elements Tom and I discussed.

Chances are if you’re reading this, you are (or are thinking about) moving to cloud. While cloud migration isn’t a new term and many people are migrating, there are a few things you should know before taking the leap. Migrating your database to the cloud is worth the hours of planning, sorting through data and running tests because if it’s not done right, it may come with more bad than good.

The saying “knowledge is power” may be a cliché, but the truth of it holds strong, especially as it relates to IT systems and processes. With all the many moving parts in IT and the overall business, employees can often feel either bombarded with information overload or uncertain without enough. For this reason, many organizations have turned to knowledge management to provide structured processes for collecting, storing, and disseminating knowledge throughout the organization.

It can be difficult to track down memory leaks, especially when deploying apps on cloud-based application services. Often teams are left with restarting their apps as the only—and less than ideal—recourse to get them back up and running. So what do you do when your cloud-based app springs a memory leak, and how do you pinpoint the cause? In this article, we’ll create a Java app designed to purposely leak memory and deploy it to DigitalOcean.

When you’re in e-commerce, page load time is crucial. Any change you make to your site can affect it, as you’ve probably found out the hard way on several occasions. So you want to make sure your site doesn’t slow down again. Or at least that when it happens, it doesn’t go unnoticed and unaddressed for any longer than it has to. Relax—you’re in the right place. In this article, we’ll examine which metrics to track and improve to keep your site in tip-top shape.

A frequently asked question when I’m speaking with SQL Sentry customers is, “Can I monitor targets across multiple domains?” The answer to this question is yes. Although there might be specific scenarios in which you’ll want to have multiple SQL Sentry installs, it’s possible to monitor targets across multiple domains through one install (i.e., one centralized SQL Sentry database). There are a couple of different options available to do so.