What should you do about memory dumps?
A SQL Server monitoring tool is warning you that you’re getting memory dumps, and you’re wondering what that means.
2019-03-15
2,724 reads
Memory
How Much Memory is “Normal” for SQL Servers?
When I look at a SQL Server, one of the first things I check is, “How much memory does this thing have relative to the amount of data we’re hosting on here?” I’ve long used some seat-of-the-pants numbers, but armed with data from SQL ConstantCare® users who opted into public data sharing, let’s do a little deeper analysis.
2018-12-07
4,464 reads
2018-06-19
908 reads
2018-06-14
893 reads
2017-07-04 (first published: 2015-12-14)
10,803 reads
SSC Clinic: Finding the rogue query
When you're getting spikes of high CPU, it's quite likely it's a rogue query. But how do you find out which query? Grant Fritchey explains, using SQL Monitor.
2012-09-13
6,232 reads
SQL Server Memory Management Explained
Author Craig Outcalt takes a deep dive into the SQL Server memory allocation and how it competes with OS memory.
2011-09-20
15,341 reads
Blogs
Using AI for Git Hooks
By Steve Jones
Recently I had someone internally ask about whether SQL Source Control supports Git Hooks....
Flyway Tips: AI Helps with Commit Messages
By Steve Jones
At Redgate, we’re experimenting with how AI can help developers and DBAs become better...
Startup scripts in SQL Server containers
I was messing around performing investigative work on a pod running SQL Server 2025...
Forums
SQL Agent job running gMSA cannot backup to NAS target
I'm running a group MSA for the database engine and SQL Agent in a...
sys.query_store_query question
All, My query is as follows: SET DATEFORMAT dmy SELECT p.query_id, DATEADD(MICROSECOND,-rs.max_duration,rs.first_execution_time) AS starttime,...
Encoding Strings
Comments posted to this topic are about the item Encoding Strings
Question of the Day
Encoding Strings
I have this code in SQL Server 2025. What is the result?
DECLARE @message VARCHAR(50) = 'Hello SQL Server 2025!'; DECLARE @encoded VARCHAR(MAX); SET @encoded = BASE64_ENCODE(@message); SELECT @encoded AS EncodedResult;See possible answers