Buying a home requires thoughtful planning and takes a significant amount of time and resources. Beyond your list of must-haves, you’ve likely kept tabs on houses of interest to you, the state of the market, how safe the neighborhood is, and more. Another factor in your decision is how the house is equipped to grow with you—will it continue to meet your needs in the next five years? It’s critical to establish a sound foundation that works for you today and in the future.

"No one likes documentation", chirped the little blue birds. The bird quotes in the image above are all taken from real tweets and are listed below for accessibility: I can't argue with "liking to write documentation" being a rare skill, since so many people are vocal about disliking it. That tweet might prove to be true, in which case, technical writers should simply be more appreciated for the rare gems that they are. In this blog post, however, I’m going to explain.

SentryOne Document supports multiple metadata sources, and we plan to expand available providers in the future. But what if you want to add a metadata source that isn’t currently supported? This is where SentryOne Document’s Custom Metadata Import, available in both the Software and Cloud edition, can help. Leveraging this provider, you can manually insert any metadata source—DB2, REST API, or others.

As a consumer, you know how you respond to slow sites. You hit the back button or close the browser. As a business owner, you’re well aware of this. You’re a consumer, too, after all. So, you know page load time and conversion rate are related. But how exactly? How does it affect the bottom line? In this article, we’ll analyze how page load time affects conversion rates and by how much.

DevOps has great potential; when it’s done right, it offers organizations improved collaboration, quick innovation, better quality, and shorter delivery cycles. But the reality is that some businesses don’t carry the DevOps process through to the data layer.

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.