As its tenth birthday approaches, Microsoft prepares to end extended support for SQL Server 2008 and 2008 R2. This date has been known since product launch, there are now less than 12 months to retire or replace aging SQL Server estates. In the past, when we hit extended support end date, that's..
Pet servers are those servers you named, nurtured (loved?). Cattle servers are disposable, numbers only. When they are sick they are “…taken out back, shot, and replaced…”. Containers offer a new way to think about the services we’re delivering – processing our cattle-like servers into something..
Due to the large number of different SQL Server instances (and versions) we support, we get the luxury of seeing unusual behaviour more often than most. Something I’ve seen three times now is a curious issue with the SQL Server Agent on SQL 2016 CU5 which rarely crops up following a..
While performing an in-place SQL Server upgrade for a customer, I came across the KB2919355 issue. This article will show you how to resolve this this problem and point out why this can be misleading.
If you’re running SQL Server 2016, you may want to install SQL Server Service Pack 1, CU8. I came across an issue recently that effectively caused the transaction log backups to hang. Through our proactive monitoring, we were alerted to the fact that a log backup had not been taken in 4 hours...
One of the common customer queries we get at Coeo is how to provide high availability for SQL Server. I have been advocating the use of SQL Server Failover Cluster Instances (FCI) to provide high availability for over 10 years. However, during a review of our reference architecture the question..
As someone who has worked with many clients across many industries one of the common problems I see is companies who are finding it hard to juggle all the adhoc requests that come in to their data team. Report requests, data modifications, minor deployments, fixes or query performance tuning; no..
Anyone that's worked with SQL for any length of time will undoubtedly have seen and heard the following
On a new installation of a SQL Server instance, by default, SQL Agent will automatically manage the job history retention, however this may not work the way you expect it to. This post explains why, and how you should set this up for best results.