The Book of Redgate: What Our Customers Say
This is from 2010, but I loved that people felt this way about Redgate Software. A lot of these words are things that we aim to express to each...
2025-11-07
18 reads
This is from 2010, but I loved that people felt this way about Redgate Software. A lot of these words are things that we aim to express to each...
2025-11-07
18 reads
In SQL Server environments where transactional replication runs alongside Always On Availability Groups (AGs), DBAs sometimes face a frustrating scenario: replication stalls when a secondary replica or subscriber is...
2025-11-07 (first published: 2025-10-21)
506 reads
It’s that time of the month again, and once again, I’m late and I’m hosting. I was traveling a lot in October and didn’t sort out hosting for this...
2025-11-07
31 reads
Today I’m in San Francisco at Small Data SF 2025. I went to the conference last year and thought it was a great event. Watching people talk about data...
2025-11-05
13 reads
For decades, enterprises have thought about data like plumbers think about water: you build pipelines, connect sources to sinks, and hope the pipes do not burst under pressure. That...
2025-11-05 (first published: 2025-10-17)
444 reads
Why you should connect resiliently to SQL Server
Transient failures happen — in the cloud (Azure SQL) and on-prem. A resilient connection strategy lets your app recover gracefully instead of...
2025-11-05 (first published: 2025-10-13)
391 reads
Welcome back, my fellow sleuths, to my mystery-inspired blog series! I’m having a ton of fun writing these, and I hope you’re enjoying the ride through SQL Server’s haunted...
2025-11-03 (first published: 2025-10-17)
297 reads
Don’t Let Trouble Sneak Up on You Most SQL Servers run quietly. Until they don’t. By the time someone notices an application outage or a failed backup, you’re...
2025-11-03 (first published: 2025-10-15)
329 reads
foilsick – adj. feeling ashamed after revealing a little too much of yourself to someone – allowing them too clear a view of your pettiness, your anger, your cowardice,...
2025-10-31
33 reads
"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help that," said the Cat: "we’re all mad here. I’m mad. You’re mad.""How do you know...
2025-10-31 (first published: 2025-10-13)
307 reads
By ChrisJenkins
You could be tolerating limited reporting because there isn’t an off the shelf solution...
A while back I wrote a quick post on setting up key mappings in...
By Steve Jones
In 100 years a lot of what we take to be true now will...
Hello, I inherited a number of tables with like 20-30 column using nvarchar(256) in...
Hi, i'm running vs2022. I'm trying out a c# script that i'd like to...
I upgraded a SQL Server 2019 instance to SQL Server 2025. I wanted to test the fuzzy string search functions. I run this code:
SELECT JARO_WINKLER_DISTANCE('tim', 'tom')
I get this error message:Msg 195, Level 15, State 10, Line 1 'JARO_WINKLER_DISTANCE' is not a recognized built-in function name.What is wrong? See possible answers