Here is the behavior that I just found out by mistake. There is a UNIQUEIDENTIFIER column in the table on SQL Server, and I ran a query like:
SELECT * FROM Tbl WHERE GuidColumn = N'2B375CD8-D210-463F-A2FD-EAFB0D643664#1'
The # 1 at the end of Guid got there by mistake, as I copied it from a URL adding # 1, # 2, # 3, etc., representing the paging.
What surprised me was that the request went fine and I got the same result as when I started:
SELECT * FROM Tbl WHERE GuidColumn = N'2B375CD8-D210-463F-A2FD-EAFB0D643664'
Does anyone know how # and anything after it has been indexed in such a scenario?
source share