At Coeo, we have the opportunity to deal with a wide range of problems every day and sometimes they manifest in mysterious ways.
Backup to URL was introduced in SQL Server 2012 SP1 CU2 and allows backups to be taken directly to an Azure Storage Account. This post will expand on the evolving syntax when using Backup to URL and what I would consider to be best practice for Storage Account access.
If you would like a more..
SQL Server 2008 and 2008 left Extended Support on 9th July 2019. In the latest episode of the Coeo Conversations Podcast Sales and Marketing Director James talks about the issue and explores the options available to businesses.
The Database Administrator (DBA) is often the organisation’s main source of technical database operational knowledge and they are difficult to obtain and retain.
At Coeo we are seeing increasing numbers of customers take their first steps towards modernising their data platforms by moving workloads to the public cloud. Here is our quick guide to the options available:
In this blog post I will talk about a very common issue in SQL Server: deadlocks.
The current world record for the number of people to fit into a Mini is 28 people. For SQL Server, the max number of databases you can have on a single SQL Server instance is 32,767. However, like the people in the Mini, just because you can cram that many databases onto one server doesn’t mean..
A common problem with data platform modernisation is gaining application vendor support for newer SQL Server versions, but that has been made easier since Microsoft’s change in position on the long-term use of database compatibility mode announced in 2018.
SQL Server 2008 and SQL Server 2008 R2 have now left Extended Support and no longer receive security updates. This blog and infographic explain what this means and how unsupported products can affect your business:
To find out when the last successful DBCC CHECKDB for a given database was, we can use the DBCC DBINFO() command and look for the dbi_dbccLastKnownGood value. Alternatively, Microsoft introduced this information in the form of a DATABASEPROPERTYEX value, starting from SQL Server 2016 SP2: