0
kicks
SQL Server 2005 bug when using LIKE searches
Here's a demo of a nice little bug in SQL Server 2005 when using LIKE comparisons for searching.
What is so "nice" about it is that it only manifests itself if your search ends in number 9 followed by a wildcard when
selecting only columns covered by a nonclustered index.