I was checking the exported estimated execution plans for all stored procs in a database, looking for table or index scans (to find missing indexes or badly written queries) and noticed that statements like

Code:
UPDATE dbo.JobSites
   SET MediaCost = @ConvertedCost,
	ComplexExplanation = @Explanation
 WHERE CURRENT OF curJobSites;
are reported as "Clustered Index Update" + "Clustered Index Scan". With insane Estimated Subtree Cost.

It doesn't look like the procedure in question is actually that slow, but it does worry me a bit.

Is this the expected estimated query plan for UPDATE...WHERE CURRENT OF... or am I doing something wrong?

The server is Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

Thanks, Jenda