SQL Server 2000 and Latching problem

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


.

Relevant Pages

  • Re: Problem with a Socket server program opening/accepting many connections and the GC is running.
    ... Yes your book is half right - it is 5 pending requests max on Workstation ... server OS if you want to do high capacity server stuff. ... clients connect and then stay connected ... As far as garbage collection killing things, ...
    (microsoft.public.dotnet.framework.performance)
  • Re: Application design question
    ... system where clients can register with the server ... The server would then keep track of these requests and everytime the data ... scheduler component first (one that can fire events based on ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Real time notification
    ... Thanks Sahil for detailed reply. ... > reaction was that I will use a database. ... > a) Logical - The central server informs the clients of a change. ...
    (microsoft.public.dotnet.framework.adonet)
  • Database Access Issue
    ... I reciently attempted to migrate a database application and a number ... of file shares from an NT4 server to a Windows 2000 server. ... XP, Mac OSX, and Mac OS 9.x. ... Following the migration all clients were able to access the file ...
    (microsoft.public.win2000.macintosh)
  • Re: 5 access 2000 users and 1 AccessXP user
    ... Access database in question is in Access 2000). ... The back end is on a server running win2K server. ... Check the permissions of the folder where the workstations are connected ... >> started upgrading my win2K clients to XP and the server is still running ...
    (microsoft.public.access.conversion)
Loading