| thejamie 2006-04-07, 8:23 pm |
| After running many days against a database that contains a few million
records, I see large numbers of the SQLDUMPER.EXE in my task manager. To
reproduce this, send a query to SQL Server that is large and requires the
full resources of the computer's RAM. Then open a related application -
specifically Visual Studio 2005. It will chew into resources that aren't
there and until I killed the Visual Studio 2005 process, my Windows task
manager was literally full of instances of SQLDUMPER.exe.
I read up on this particular object and the articles claimed a bug for this
in SQL Server 2000 was plugged when SP4 arrived on the scene. The bug states
that opening a cursor with the same name as one in another routine required
deallocation prior to use.
Is there a remote possibility that when a query runs in SQL Server 2005,
that it uses resources that are pooled for Visual Studio 2005 to use and when
they collide, SQLDumper.exe is launched? Can anyone explain the why's and
wherefore's of how this may be occuring?
--
Regards,
Jamie
|