Re: Problem with reading in packet mode

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Kevin,

Yes, I have the latest MDAC version: MDAC 2.8 SP1 on WINDOWS XP SP2.

It's true, the performance gets much better when we increase the packet size
(we already knew that), as follows:
- for packet size 512 I get aprox. 7 secs (compared to 49 secs)
- increasing packet size over 512 won't improve performance anymore

The bottom line is: even when using larger values for the packet size,
performance is still poor compared
to the case when SQLSetStmtOption is called after SQLExecDirect (7 secs vs.
1 sec). Why is that happening ?
So, increasing packet size is a good workaround but up to a point.

There is the following bussiness impact: the customers using our application
are asking questions about this (strange) behaviour. Is there any
Microsoft doc, release note, etc. that refers to it ?

Could this issue be escalated such that, at least, we could get an official
answer from Microsoft regarding this behaviour. This would prove at
least that we are not misusing the ODBC API in any way (this was our main
concern in the first place because, actually, the order of ODBC
calls causes this strange behaviour).

Your help is appreciated.

Regards,
Ovidiu


"Kevin Yu [MSFT]" <v-kevy@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:hYsGn42hFHA.944@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Ovidiu,
>
> What is the version of MDAC on your machine? Please try to upgrade to the
> latest version MDAC 2.8 sp1 from the following link to see if it can
> resolved the problem.
>
> http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-
> a9e0-3a1afbd5922e&DisplayLang=en
>
> Also I suggest you try to set to a larger packet size (e.g. 512).
>
> Kevin Yu
> =======
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
>


.