Re: ODBC, SQL Server, Frustration
- From: "Matt Neerincx [MSFT]" <mattn@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 18 Sep 2005 23:12:46 -0700
So you never see the INSERT INTO make it to the SQL Server in SQL Profiler?
If you don't see it make it to the server, this indicates a problem with the
driver.
If you do see it make it, I would suspect blocking on server side, for
example you could have an open transaction that is blocking the insert.
If it hangs on the client side and nothing makes it to SQL Profiler, then
what I would do is compare the dll versions of all the drivers on QA versus
other machines.
Look specifically at sqlsrvr32.dll in windows\system32 folder, compare these
on good and bad machines. You can also try swapping them out this dll is
not system file protected.
--
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Arnie" <none> wrote in message
news:e1uNyDvrFHA.2880@xxxxxxxxxxxxxxxxxxxxxxx
> Warren Read wrote:
>> Were you able to resolve this? It isn't a situation that i've ever
>> heard of. Perhaps upgrading to MDAC 2.8 would help?
>>
> Thanks for the reply. Nope, no solution yet. My original post was
> incorrect. Two of the three servers are W2K3, the other is W2K. The
> problem server is one of the W2K3 ones.
>
> I just don't know where to go from here. The ODBC trace and server-side
> trace didn't show anything. I don't know where else to look. The worst
> thing is that each of our three groups have three servers; one each for
> SQL Server, Oracle and DB2. The SQL Server for QA is the only place the
> problem occurs.
>
> Any suggestions from anyone, no matter how off the wall, would be
> appreciated.
>
> - Arnie
>
.
- References:
- RE: ODBC, SQL Server, Frustration
- From: Warren Read
- Re: ODBC, SQL Server, Frustration
- From: Arnie
- RE: ODBC, SQL Server, Frustration
- Prev by Date: Re: Multi user application
- Next by Date: Re: "INI File is corrupt" error message
- Previous by thread: Re: ODBC, SQL Server, Frustration
- Next by thread: ODBC Data Source Administrator error
- Index(es):
Relevant Pages
|
Loading