ODBC SQL Server Driver connection issues

Issue:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (rec
v()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
above error is recieved during a heavy SQL query from Query Analyzer & a
OLEDB application client. Other queries like sp_who2 operate fine.
Environment:
SQL Servers running both SQL 2000 & 2005 (currently disabled) patched and
hotfix'd to most recent. Windows 2003 Servers patched and hotfix'd also. MDA
C
2.8.
Interestingly, when the query is run with SQL Server Management Studio it
runs just fine. Is there a compatiblity issue running both of these SQL
server versions on the same machine? When I run the query from a different
machine without the server software, just the two client versions I don't
experience this network connectivity issue.
ThanksOn May 24, 9:33 pm, Outlook 2003 user
<Outlook2003u...@.discussions.microsoft.com> wrote:
> Issue:
> [Microsoft][ODBCSQL Server Driver][DBNETLIB]ConnectionRead (re
cv()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> above error is recieved during a heavy SQL query from Query Analyzer & aOL
EDBapplication client. Other queries like sp_who2 operate fine.
> Environment:
> SQL Servers running both SQL 2000 & 2005 (currently disabled) patched and
> hotfix'd to most recent. Windows 2003 Servers patched and hotfix'd also. M
DAC
> 2.8.
> Interestingly, when the query is run with SQL Server Management Studio it
> runs just fine. Is there a compatiblity issue running both of these SQL
> server versions on the same machine? When I run the query from a different
> machine without the server software, just the two client versions I don't
> experience this network connectivity issue.
> Thanks
Check for registry setting SynAttack in KB|||Thanks, but I added that a while ago with no success.
"M A Srinivas" wrote:

> On May 24, 9:33 pm, Outlook 2003 user
> <Outlook2003u...@.discussions.microsoft.com> wrote:
> Check for registry setting SynAttack in KB
>|||Just a follow-up to my post.
I figured out that the TOE was not operating correctly. This situation was
happening on new DELL 2950 & 1950 Servers with TCP/IP Offloading Engine
enables. After completely disabling this feature, via Microsoft & DELL
hardware the erroneous ODBC error stop occurring.
Thanks,
Outlook 2003 User (lol)
"Outlook 2003 user" wrote:
[vbcol=seagreen]
> Thanks, but I added that a while ago with no success.
> "M A Srinivas" wrote:
>

ODBC SQL Server Driver connection issues

Issue:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
above error is recieved during a heavy SQL query from Query Analyzer & a
OLEDB application client. Other queries like sp_who2 operate fine.
Environment:
SQL Servers running both SQL 2000 & 2005 (currently disabled) patched and
hotfix'd to most recent. Windows 2003 Servers patched and hotfix'd also. MDAC
2.8.
Interestingly, when the query is run with SQL Server Management Studio it
runs just fine. Is there a compatiblity issue running both of these SQL
server versions on the same machine? When I run the query from a different
machine without the server software, just the two client versions I don't
experience this network connectivity issue.
Thanks
On May 24, 9:33 pm, Outlook 2003 user
<Outlook2003u...@.discussions.microsoft.com> wrote:
> Issue:
> [Microsoft][ODBCSQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> above error is recieved during a heavy SQL query from Query Analyzer & aOLEDBapplication client. Other queries like sp_who2 operate fine.
> Environment:
> SQL Servers running both SQL 2000 & 2005 (currently disabled) patched and
> hotfix'd to most recent. Windows 2003 Servers patched and hotfix'd also. MDAC
> 2.8.
> Interestingly, when the query is run with SQL Server Management Studio it
> runs just fine. Is there a compatiblity issue running both of these SQL
> server versions on the same machine? When I run the query from a different
> machine without the server software, just the two client versions I don't
> experience this network connectivity issue.
> Thanks
Check for registry setting SynAttack in KB
|||Thanks, but I added that a while ago with no success.
"M A Srinivas" wrote:

> On May 24, 9:33 pm, Outlook 2003 user
> <Outlook2003u...@.discussions.microsoft.com> wrote:
> Check for registry setting SynAttack in KB
>
|||Just a follow-up to my post.
I figured out that the TOE was not operating correctly. This situation was
happening on new DELL 2950 & 1950 Servers with TCP/IP Offloading Engine
enables. After completely disabling this feature, via Microsoft & DELL
hardware the erroneous ODBC error stop occurring.
Thanks,
Outlook 2003 User (lol)
"Outlook 2003 user" wrote:
[vbcol=seagreen]
> Thanks, but I added that a while ago with no success.
> "M A Srinivas" wrote:

ODBC Isolation level

Hello Guys,

Is there any way I can set up the isolation level on the ODBC settings
I have a MFC application, it connects to the SQLServer 2000 , but I would like to set up the Isolation level to UR (uncommitted read), is this
possible ?

I have tried setting this up by means of the Query analyser but this only work during that session it does not affect any of the others connections to the database.

My app is a involves heavy OLTP transactions and I am performing a pseudo stress testing..

thank you for your helpIt is my understanding that this setting is per session. I asked our specialist the same question (dirty reads will do just fine here for our 'brochure' website but the default is read committed?) and was told that this setting was per session. (more later)|||Originally posted by Hollerith
It is my understanding that this setting is per session. I asked our specialist the same question (dirty reads will do just fine here for our 'brochure' website but the default is read committed?) and was told that this setting was per session. (more later)

hey thanks for your help, in the same topic
can you do this

selec foocolum from footable with (nolock) <-- is this correct

thanks

marcos oliva