Getting Sneaky With Forced Parameterization
In which Erik works around the documented limitations with CROSS APPLY.
2018-12-19
2,722 reads
In which Erik works around the documented limitations with CROSS APPLY.
2018-12-19
2,722 reads
If you can't get forced parameterization to work due to variables, try using a temp table instead.
2018-12-14
3,219 reads
I have heard about parameterization for SQL Server queries, but what is Forced and Simple Parameterization and which one should I use for my SQL Server database?
2013-05-10
5,199 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