Re: SQL Server 2000 and Latching problem
- From: "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx>
- Date: Mon, 5 Sep 2005 14:56:45 -0400
Are these mostly read only requests or do they involve Inserts, Updates and
Deletes? That seems pretty limiting to have only a single thread processing
these requests. In any case that is no where near enough info to determine
what the issues are. My guess would be lack of proper indexes or poorly
formed queries. How much ram on the SQL Server? Oh and is there anything
else on the same server other than SQL Server?
--
Andrew J. Kelly SQL MVP
"Simon Goss" <s.goss@xxxxxxxxxxxx> wrote in message
news:R1BL71isFHA.8272@xxxxxxxxxxxxxxxxxxxxxxxxxxx
> hi all.
>
> got a question - wondered if you guys have come across this.
>
> I have an application that acts as a database "server" where it captures
> requests for information from many clients (1-100+ but 30 is typical)
> where it then interrogates a SQL server database on their behalf, and
> then returns the results. Its a single-threaded application, so various
> clients requests have to be queued.
>
> anyway - this is working ok, except ive noticed that occasionally my
> single connection to the odbc server seems to freeze for about 300sec
> before going on a bit more accepting some more connections and then
> freezes again.
> Searches on MS technet show this is evidence of latching - and also
> event log confirms this. advice from microsoft is - keep ldf and mdf on
> separate physical devices as latches are usually caused by i/o unable to
> keep up with the application. so we have done this, but still getting
> latches when the activity of the "server" (the gateway between the
> application clients and the sql server) seems to rise. worst case, the
> gateway application can be dealing with a request every 1ms , but i
> would have thought anywhere between 1-10ms is average - its not flat out
> all the time.
>
> so - i suppose the short question is - is there any way i can avoid
> latching completely? its an application that used to use ISAM database
> format, but this new gateway "captures" isam-style requests for info and
> converts them to a sql request as this is where the info is stored now.
> it was considered too expensive to rewrite the client software, so we
> emulate an ISAM situation by realtime "translation" of isam<->SQL
>
> any thoughts anyone ? please feel free to email me here or directly -
> but id really appreciate any pointers!
> thanks!
> -s
>
>
> _____________________________________
>
> Simon Goss
> Senior Products Consultant
> Marval Software Limited
>
>
.
- Follow-Ups:
- SQL Server 2000 and Latching problem
- From: Simon Goss
- SQL Server 2000 and Latching problem
- References:
- SQL Server 2000 and Latching problem
- From: Simon Goss
- SQL Server 2000 and Latching problem
- Prev by Date: SQL Server 2000 and Latching problem
- Next by Date: Re: Connect Problem with 2000 Advanced -> 2003 Server
- Previous by thread: SQL Server 2000 and Latching problem
- Next by thread: SQL Server 2000 and Latching problem
- Index(es):
Relevant Pages
|
