Hi Lora
As far as I know, Isodat does not run a sqlserv.exe process.  Unless it is part of the Xcalibur setup and you are using Thermo's Xcalibur data handling software, the Isodat installation should not have this process running. It is from something else.

It may be a worm that made it to your machine somehow; see:
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_SDBOT.BZO&VSect=T

Gilles

Gilles St-Jean
Chercheur / Research Scientist
Université d'Ottawa / University of Ottawa
Sciences de la Terre / Earth Sciences
140 Louis Pasteur, Ottawa, Ontario, Canada K1N 6N5
Tel: 1-613-562-5800 xt 6830 (Bureau / Office)
                    xt 6839 (Bureau / Office Lab)
                    xt 6836 (IRMS lab)
Téléc. / Fax: 1-613-562-5192
Courriel / E-mail: [log in to unmask]
Toile / Web: www.isotope.uottawa.ca

-----Message d'origine-----
De : Stable Isotope Geochemistry [mailto:[log in to unmask]] De la part de Lora L. Wingate
Envoyé : 19 avril 2007 10:55
À : [log in to unmask]
Objet : [ISOGEOCHEM] Isodat NT--ending sqlservr.exe process?

We are running Isodat NT SP 2.49 on Windows XP (Kiel IV/MAT253).  The 
computer is presently completely isolated from the network.
I've noticed that the sqlserv.exe process takes up a lot(!) of memory.  Has 
anyone tried ending that process, or know whether it is necessary for the 
proper function of Isodat?  I haven't seen it bundled with other XP 
installations, so I'm curious as to what it actually does.  My web searches 
have yielded a mixed bag of answers, and so I'm wondering if anyone has 
tried killing that process (especially running a Kiel) and what result(s) 
that had.  Thanks for any insight...







Lora L. Wingate
University of Michigan
Department of Geological Sciences
Stable Isotope Laboratory
1100 North University
1013 C.C. Little Building
Ann Arbor, MI 48109-1005