none
What is SQLDumper.exe doing ?

    Question

  • In the task manager, we only have 2 processes with username "sql_ssas_srv", and these are msmdsrv.exe and SqlDumper.exe

    This tells me that SqlDumper.exe is related to SSAS.

    SQLDumper.exe appears for a fraction of a second at a time, every couple of seconds. What is this process doing ?

     

    Thursday, October 26, 2006 9:33 AM

Answers

  • This is not a good thing to see SQLDumper.EXE. It means the Analysis Services process is crashing and creating a dumpfile. You should see a file for each time SQLDumper ran or in reality when AS crashed, it will be located in the C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Log folder. I may be wrong on the location.

    This actually is a very useful tool for support to determine what is happening to the server. Support may ask you to change some property settings to get a full memory dump, and then recreate the problem again.

    I would keep a close eye on it to see when SQL Dumper is executing, during processing or heavy query loads and make a call into support.

    David

    Mariner

    Thursday, October 26, 2006 11:45 PM
  • Click on the "Script" button in the Server properties dialog and modify resulting script. Remove anything between <QueryLogConnectionString> </QueryLogConnectionString>

    Edward Melomed.
    --
    This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, October 31, 2006 3:01 AM
    Owner

All replies

  •  

    As described in the KB article at http://support.microsoft.com/Default.aspx?kbid=917825, you can use the Sqldumper.exe utility to generate a dump file on demand for any Microsoft Windows application. For example, you can generate a dump file for debugging an application problem when a computer that is running SQL Server 2005 is not responding to user requests. A dump file can be a mini-dump file, a full dump file, or a filtered dump file.

    However, you cannot use the Sqldumper.exe utility for general purpose debugging. For more information about general purpose debugging, visit the following Microsoft Web site:

    http://www.microsoft.com/whdc/devtools/debugging/default.mspx (http://www.microsoft.com/whdc/devtools/debugging/default.mspx)

    The SQL Server process calls the Sqldumper.exe utility internally to generate a dump file when the process experiences any exceptions. SQL Server passes flags to the Sqldumper.exe utility. You can use trace flags to change the flags that SQL Server passes to the utility in the context of an exception or in the context an assertion. These trace flags are in the range from 2540 to 2559. You can use these trace flags to generate certain types of dump files.

    Hope this helps,

    Artur

    Thursday, October 26, 2006 8:16 PM
  • This is not a good thing to see SQLDumper.EXE. It means the Analysis Services process is crashing and creating a dumpfile. You should see a file for each time SQLDumper ran or in reality when AS crashed, it will be located in the C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Log folder. I may be wrong on the location.

    This actually is a very useful tool for support to determine what is happening to the server. Support may ask you to change some property settings to get a full memory dump, and then recreate the problem again.

    I would keep a close eye on it to see when SQL Dumper is executing, during processing or heavy query loads and make a call into support.

    David

    Mariner

    Thursday, October 26, 2006 11:45 PM
  • You're bl**dy right!

    I looked in the Log directory, and sure enough there were fifteen thousand of minidumps in there.

    I'm going to call MS first thing Monday morning.

     

    Sunday, October 29, 2006 10:07 PM
  • OK, by looking at the Event log, it turns out that SSAS is having difficulties writing to the query log.

    In the SSAS Server Properties, I'm trying to remove the connection string from the "Log\QuerryLog\QueryLogConnectionString", but it's not letting me. I could remove the name of the QueryLogTableName though. I've also set CreateQueryLogTable to false.

    QueryLogFileName is empty and allways has been.

    Anyone knows how to disable Query logging completely ?

    Sunday, October 29, 2006 10:21 PM
  • Click on the "Script" button in the Server properties dialog and modify resulting script. Remove anything between <QueryLogConnectionString> </QueryLogConnectionString>

    Edward Melomed.
    --
    This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, October 31, 2006 3:01 AM
    Owner