Re: A lot of sp_cursorfetch in profiler.
From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 02/15/05
- Next message: rgn: "Re: Suspect Databases and Hidden Attributes"
- Previous message: Agoston Bejo: "Re: Log everything"
- In reply to: Geir Holme: "A lot of sp_cursorfetch in profiler."
- Next in thread: Vinod Kumar: "Re: A lot of sp_cursorfetch in profiler."
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 15 Feb 2005 11:31:46 +0100
You should open a "firehose" cursor, AKA "default resultset", AKA adOpenForwardOnly (try this
attribute on your recordset).
-- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "Geir Holme" <geir@multicase.no> wrote in message news:OQ2SDd0EFHA.3536@TK2MSFTNGP15.phx.gbl... > Hi all. > I am looking at some profiler logging and gets a lot of the lines looking like: > > exec sp_cursorfetch 180150024, 2, 0, 1 > > > This comes after running a simple prosedure that select some lines. > > All i VB6. I guess it has something to do on how we retrieve data (ADO). Does anyone have a few > hints on where to look to get rid of all these lines. Or what to try. > > > thanx all. > > geir >
- Next message: rgn: "Re: Suspect Databases and Hidden Attributes"
- Previous message: Agoston Bejo: "Re: Log everything"
- In reply to: Geir Holme: "A lot of sp_cursorfetch in profiler."
- Next in thread: Vinod Kumar: "Re: A lot of sp_cursorfetch in profiler."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|