2019-01-18
681 reads
2019-01-18
681 reads
2018-06-26
879 reads
2018-01-18
833 reads
Of course we all like our colleagues to think that we know everything there is to know about SQL Server Collations. However, the truth is that it is a rather complicated topic to fully understand and the cost of getting collation wrong can be great. If only one could ask certain questions on forums or at conferences without blushing. Help is at hand, because Robert Sheldon once again makes the complicated seem simple by answering those questions that you were too shy to ask.
2017-06-15
3,969 reads
In some scenarios we can find different SQL Server collations between the server instance and its databases. Douglas P. Castilho explains a simple way to correct the collations in a few steps.
2017-04-11
3,262 reads
SQL Server collation is an important setting when creating database objects. One of the best ways to ensure that collation issues do not happen is to ensure that the collation settings are properly specified in the script that generates the database objects - Siddharth Mehta demonstrates how to do this.
2016-10-07
4,085 reads
Changing Database Collation Through Primary keys, Foreign Keys, Default and Check Constraints and more.
2016-03-07
4,199 reads
2014-11-11 (first published: 2014-07-25)
2,637 reads
Most DBAs, myself included, install SQL Server with the default server collation SQL_Latin1_General_CP1_CI_AS and all of our table columns get created using this default setting. This tip will look at the performance impacts of querying data with this setting as it compares to querying columns with the collation set to SQL_Latin1_General_CP1_CS_AS.
2014-05-06
4,752 reads
2014-01-17
1,938 reads
By Steve Jones
I haven’t done one of these in awhile, but I saw an article recently...
In last months one of the scenarios where you can use AI has been...
Comments posted to this topic are about the item Missing the Jaro Winkler Distance
Comments posted to this topic are about the item 25 Years Later: What SQLServerCentral...
Comments posted to this topic are about the item Doing Good at SQL Server...
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