A good DBA always monitors what’s written to the Error log and trying to make sense of what’s happening on the server or look for potential issues or look for any traces something other than ordinary is happening.
If you are using CTP1 of DENALI, the next version of SQL Server and using Extended Events there is a good chance you might see the message “Using ‘dbghelp.dll’ version ’4.0.5′” written to the error log more than few times. Have you wondered what is this message and who is writing this or is there something fishy going on the server?
This post will try to shed some light on this and make sense of the behavior. Every time you query the files generated by the Extended Events using the code snippet like below, the message “Using ‘dbghelp.dll’ version ’4.0.5′” is being written to the error log.
--Lets see if we got any activity SELECT CAST(event_data AS XML) AS xmldata FROM sys.fn_xe_file_target_read_file ( 'C:\SQLserver\XEvents\TrackConnectionPool*.xel' , 'C:\SQLserver\XEvents\TrackConnectionPool*mta' , null , null )
You might wonder why does Extended Events need to write that message to the error log. It is simply because reading the files generated by Extended events using sys.fn_xe_file_target_read_file leads to “sql dumper” being called and the fact “sql dumper” program was used is written to the error log.
Should I be worried because of this message? Not really and it is a very benign message and its being written simply because of the api (sql dumper) being used while reading the Extended event files.