Why does SQL Server think that CHAR(49) AND CHAR(185) are the same?
When a 1 is entered into a column either of type NVARCHAR or TEXT, it sees it as both CHAR (49) (One) and CHAR (185) (Superscript One)
Example data:
SELECT CAST('1111' AS TEXT) AS col1 INTO CharTest;
Select scripts:
SELECT * FROM CharTest WHERE col1 LIKE '%'+CHAR(49)+'%';
SELECT * FROM CharTest WHERE col1 LIKE '%'+CHAR(185)+'%';
Both statements return: 1111