RE: Protocol Error in TDS Stream vs Network Packet Size
- From: "Gavin Chan" <GavinChan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 3 May 2005 03:52:04 -0700
We reported this problem and finally we confirmed that it is a bug.
For MSQuery, ODBC driver is used which has a problem in retrieving large
recordset. With our default setting in SQL Server - Network Packet Size =
4096, the field definition for the recordset is too large to fit in one
network packet and ODBC driver do not handle this properly and the problem
occur. Microsoft said that a fix will be available in next version of Windows
.....
"Gavin Chan" wrote:
> Do you mean that query the server locally by ms excel and msquery? We didn't
> try that before. However, if we are using query analyzer, this problem did
> not occur.
>
> We can simulate the same problem with Excel 2000, XP and 2003. If this is a
> bug, it seems to be related to SQL Server. We are using SQL Server 2000 + SP3
> (8.00.847) but I am not able to find any fix that is related to the problem.
>
> "Kevin McDonnell [MSFT]" wrote:
>
> > It could be a bug, however everyone's network could impact the behavior.
> > Does this also occur if you were to query the server locally?
> >
> > Thanks,
> >
> > Kevin McDonnell
> > Microsoft Corporation
> >
> > This posting is provided AS IS with no warranties, and confers no rights.
> >
> >
> >
> >
.
- Prev by Date: Re: dts packages take a long time to run
- Next by Date: Cannot Connect to Instance
- Previous by thread: dts packages take a long time to run
- Next by thread: Cannot Connect to Instance
- Index(es):
Relevant Pages
|
