About this document

Resolving SQL Implicit Conversion Issues by carlos is a document available to read on EtoBox.

The document describes a performance issue when querying a SQL Server database table. When filtering on the primary key column, which was defined as a character string but stored numeric values, the queries performed a full table scan instead of an index seek. This was caused by SQL Server implicitly converting the character string column to a number when comparing it to the numeric filter value. Changing the filter to use a string value instead resolved the issue and allowed the more efficient index seek.

Author

carlos

Language

EN