2015-04-14
1,795 reads
computed columns
2014-04-30
1,954 reads
2013-11-15
2,007 reads
2013-01-31
2,298 reads
A Computed Column Defined with a User-Defined Function Might Impact Query Performance
A benefit of using computed columns is that they can save developers from having to write calculation logic at the application layer; at the table level, the application can simply reference the computed column. In addition, performance can be improved by persisting a computed column and building an index on it.
2012-02-03
2,708 reads
2012-01-31
2,363 reads
2010-09-30
2,935 reads
2010-07-21
4,081 reads
Blogs
RANK() vs DENSE_RANK(): #SQLNewBlogger
By Steve Jones
I haven’t done one of these in awhile, but I saw an article recently...
Using CAT for Testing of Data Agents
In last months one of the scenarios where you can use AI has been...
Forums
Missing the Jaro Winkler Distance
Comments posted to this topic are about the item Missing the Jaro Winkler Distance
25 Years Later: What SQLServerCentral Meant to Me
Comments posted to this topic are about the item 25 Years Later: What SQLServerCentral...
Doing Good at SQL Server Central
Comments posted to this topic are about the item Doing Good at SQL Server...
Question of the Day
Missing the Jaro Winkler Distance
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