![coda 2 replace special characters coda 2 replace special characters](https://i.stack.imgur.com/GHRd0.png)
#Coda 2 replace special characters update
There are far too many variations to give examples for here so I will try to post a detailed explanation on my blog sometime soon (and then will update this with the link to it). And the range of a-Z won't match any characters in a binary Collation (one ending in either _BIN or _BIN2, but don't use _BIN) given that the value of A is 65 and a is 97, hence it is an invalid range of 97 through 65 -). The effect will be that a will be within the range of A-Z for one of them, but not the other. Meaning, assuming a case-sensitive Collation for both types of Collations, one will do AaBb. For example, the SQL Server Collations sort upper-case and lower-case letters in the opposite order as the Windows Collations. Of course, what those extra characters would be is on a per-Code Page basis.Īlso, please be aware that both Collation type (SQL Server vs Windows) and sensitivity settings (case, accent, etc sensitive vs insensitive) will affect which characters are included in a particular range. Þ = Latin capital "Thorn" = SELECT CHAR(0xDE)), then you might need to include those in the character class. If you are guaranteed to only ever use the 26 letters of the US English alphabet (both upper-case and lower-case versions) then sure, you can get away with using LIKE and/or PATINDEX with the simple range notation of (you wouldn't need to use an upper-case "Z" when using a case-insensitive Collation).īut, if you might get characters not found in the en-US alphabet yet available in various Code Pages / Collations for VARCHAR data (e.g.