Several of the instances in an Availability Group (AG) that I look after, have some of the Temp DB data files stored on the C: drive. This is generally not a good idea – certainly when you have another drive allocated for the TempDB. All TempDB files need to be in the correct location and moving them isn’t as difficult as some people would appear to believe.
Continue reading
Some time ago, I wrote an article that used the OUTPUT clause with the MERGE statement. It was a more complicated example of using OUTPUT, so I feel that more basic examples are required, to reflect a more common scenario I frequently encounter.
Continue reading
In an earlier article, I described how to set up a cluster and AG in Hyper-V. For an issue that I am now researching a solution to, I require an additional drive on my SQL Server environments. Adding a new drive to a Hyper-V VM is fairly straightforward but I had to dig around a little.
Continue reading
One thing everybody should realise, is that SQL Server is a huge product – you’ll never learn all of it. Therefore, you shouldn’t feel embarrassed when you learn something that others around you might take for granted.
Reviewing somebody’s code, I came across a segment of the procedure that made no sense to me. As I knew the person who wrote the code is not generally prone to basic errors, I assumed the issue was with my understanding. Surely enough, I have discovered something that I found quite entertaining – you can update a table via the Common Table Expression (CTE) that is linked to it.
In previous articles I wrote about how you check that Instant File Initialization (IFI) is set, and how to set it. At the time, it was not available for the Log file. This has now changed.
Continue reading
In a previous article I demonstrated how to use a Distributed Availability Group (DAG) to move an Availability Group (AG) from one domain to another.
Of course, there are things to watch out for.
Continue reading
Over the past year I have been working on a project to migrate a 4-node AG with multi-terabyte databases, to another AG in a Cloud environment. To add to the fun, the downtime had to be kept to an absolute minimum.
Continue reading
For a future article, I require a Listener for the Availability Group (AG) that was created from this article.
This post describes the simple steps required to create a Listener.
Continue reading
As part of a series of development actions, we need to replace our SQL Server 2012 installations with SQL Server 2017. This is a four-node Availability Group (AG) for a system that is required 24/7 – so downtime is best avoided.
Continue reading
When upgrading a SQL Server installation to SQL2017, SQL Server Reporting Services (SSRS) is now a stand-alone installation. This short article lists the main issues that we encountered, as best as I can recall.
Continue reading
Notes on SQL 