Author: Phil Grayson

Solving data & infrastructure issues with xTEN and via our application, Aireforge.

Is it “index create memory” or “index create memory (KB)”?

I was updating an Aireforge Advise fix script and as it's important that we're using the correct syntax, I double check everything. Including commands that I've been using for 18 years as they can change between versions. I checked a few articles including TechNet, Microsoft Docs and some popular forums. All of them referenced index create … Continue reading Is it “index create memory” or “index create memory (KB)”? →

Comparing SQL Server configurations with Aireforge Studio

For ease of maintenance and performance reasons, we always aim to standardised our SQL Server estates (some of which contain over 100 instances). Everything is synchronised for their specific workload pools, so all search servers and all reporting servers are identical etc. Not only do we standardise the hardware or the VMs, but we ensure … Continue reading Comparing SQL Server configurations with Aireforge Studio →

Testing WMI for Redgate SQL Monitor

I tend to use Redgate SQL Monitor when diagnosing hard to find issues or when helping teams to better understand their estates. Sometimes, we run into issues with the network during the installation which is usually down the Windows Management Instrumentation (WMI) ports. SQL Monitor uses WMI calls to get all the non SQL Server … Continue reading Testing WMI for Redgate SQL Monitor →

Simple things SQL Servers is missing

I'm writing an article covering common SQL Server configuration issues and as I write about how Microsoft have addressed some of these in SQL Server 2016, I started thinking about what they've missed or what they should include in the next release, be it SQL Server 2018 or version 14. RCSI as the default isolation level … Continue reading Simple things SQL Servers is missing →

Why we went straight to OmniCompare 0.9 and what’s new?

So we talked a lot about 0.8.3 and how great it would be but then skipped it and went straight to 0.9.0. First of all, apologies for promising an upgrade and then delaying it but we had good reasons for this. Version 0.8.3 was supposed to include a couple of new features (mainly CLI) and … Continue reading Why we went straight to OmniCompare 0.9 and what’s new? →