Resolutions found with SQL Server and other types of databases
Problem: A developer reach out to me about an error they were getting when attempting to run a stored procedure that used a linked server to pull data from an … Continue Reading →
Someone asked me to look at this error when applying a cumulative update on an instance of SQL Server 2016. It was a strange error because I was able to … Continue Reading →
This is a quick query that I use to check if the on the stats job that ran over night. Much faster then running the “SHOW STATISTICS” for each table. … Continue Reading →
I was patching an old SQL Server 2014 server with Service Pack 3. During the update process, the Service Pack froze at the “Install_sql_common_core_Cpu64_Action : InstallFinalize” for about ten minutes … Continue Reading →
When troubleshooting from SSMS, I need to know which Windows server my clustered instance is running on. Surprised that this query is not already on the first page of the … Continue Reading →
Sadly I have not found a better way to view the available OLE DB Providers on a server. Even though I am using an out of support Windows Server 2012 … Continue Reading →
Working with large sql statements, I find it is easier to have line numbers in the query window. Enabling “Line numbers” process is the same with every version of SQL … Continue Reading →
Recently I received the following error from one of my SQL Servers: Audit: Server Audit: 65536, State changed from: STARTED to: SHUTTING_DOWN Error: 33059, Severity: 16, State: 1. An error … Continue Reading →
Teradata systems have a couple of command-line utilities to verify the health of a Teradata node. Both these command-line utilities are good to run when looking for something like hardware … Continue Reading →
The “node.check” utility has been been around for a while with Teradata. Recently I was working with Teradata’s Hardware Support team, and watched them use this utility to uncover a … Continue Reading →