Posted by Erland Sommarskog on 06/19/07 10:29

(szymon.strus@gmail.com) writes:
> Updating statistics didn't changed anything. Running the query from
> the query analyzer takes about 5 seconds for both servers. Cursor from
> my example is keyset-driven. Database Tuning Advisor for the specified
> query created few indexes but it also hasn't speed up execution of
> query.

Next step would be to try DECLARE CUSROR KEYSET from Query Analyzer on both
servers. The plan for a keyset or a dynamic cursor can be quite different
from the plan for a specific query.

Do you really need a keyset-driven cursor? Could a static cursor do?


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: DateTime
• Prev in forum: Re: mdac 2.8 and sql 2005 cursor performace issue
• Thread view: Re: mdac 2.8 and sql 2005 cursor performace issue

[Reply to this message]