Getting a query to index seek (rather than scan)

Question

Running the following query (SQL Server 2000) the execution plan shows that it used an index seek and Profiler shows it\'s doing 71 reads with a duration of 0.

Answer 1

Now you've added the schema, please try this. SQL Server treats length differences as different data types and will convert the varchar(13) column to match the varchar(20) variable

declare @p varchar(13)

If not, what about collation coercien? Is the DB or server different to the column?

declare @p varchar(13) COLLATE Latin1_General_CI_AS NOT NULL

If not, add this before and post results

SET SHOWPLAN_TEXT ON
GO