We just installed SP3 and the cursor behaviors changed, does anyone know
anything about that? I call this stored procedure from DTS:

DECLARE Queue_cursor
SCROLL CURSOR FOR SELECT SOURCE_PATH,COMPANY, TABLE_NAME FROM
dl.dbo.companies
OPEN Queue_cursor
FETCH ABSOLUTE @lineNumber FROM Queue_cursor
CLOSE Queue_cursor
DEALLOCATE Queue_cursor

If the cursor returns more than one row I get the number of rows
instead of
the selection!

Ahmed B. Zayan (ahmed.@zayan.com) writes:
> We just installed SP3 and the cursor behaviors changed, does anyone know
> anything about that? I call this stored procedure from DTS:
>
> DECLARE Queue_cursor
> SCROLL CURSOR FOR SELECT SOURCE_PATH,COMPANY, TABLE_NAME FROM
> dl.dbo.companies
> OPEN Queue_cursor
> FETCH ABSOLUTE @lineNumber FROM Queue_cursor
> CLOSE Queue_cursor
> DEALLOCATE Queue_cursor
>
> If the cursor returns more than one row I get the number of rows
> instead of the selection!

Could you provide a script that runs on the Northwind database and
which exposes the problem when you run it from Query Analyzer?

If the problem does appear when you run from QA, maybe there are some
surprises in DTS. In such case you should try microsoft.public.sqlserver.dts
The people there probably needs to see your DTS code too.

--
Erland Sommarskog, SQL Server MVP, sommar@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp