Query memory grants part 2: Varchars and sorting
Why the heck did we make all our columns varchar? That’s a hypothetical question, please.
But now we have to pay...
2019-01-09
133 reads
Why the heck did we make all our columns varchar? That’s a hypothetical question, please.
But now we have to pay...
2019-01-09
133 reads
Disclaimer: I’m still learning PowerShell. I’ve been using it more lately and I want to talk about it more. I’ll...
2019-01-08
313 reads
This is post 3 in the series about query fingerprints. Here’s the previous posts in this series:
Query HashSQL Handle
What is...
2019-01-07
799 reads
I like public speaking, but I haven’t always liked it. It started when I read Dale Carnegie’s book on public...
2019-01-05
39 reads
Let’s talk about how queries use memory, specifically in the execution plan. One of the query operators that use memory...
2019-01-04
195 reads
If you’re on SQL Server 2016 or above, maybe you’re thinking about using the Query Store. That’s good! It’s an...
2019-01-03
1,536 reads
I know this post might sound obvious. This is a very rare problem. But this actually happened to me, and...
2019-01-02
45 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