Hello,
I ran into an issue with all these logs made by default.
Disk space crunch leading to performance degradation.
OK, I moved the log dir outside the default app volume (Script/restart) onto a 100GB drive I use for the SQL transactions logs, but.
Analysis Services accumulated 20GB of logs in 2-3 days, did not clean-up the old stuff and led to disk space alerts and applications performance issues. All this with out of the box settings.
The server has in the 30 to 60 connections alive around the clock with each of these connections performing queries every 2-3 seconds or so.
I also use the query log function for optimisation purposes but for that one I log to table on a specific drive.
I run Analysis services 64 bits build 9.00.2047
Log files eating the drive have name like msmdsrv.log, FlightRecorderCurrent.trc, FlightRecorderBack.trc, SQLDmpr4495.mdmp, SQLDmpr4495.log and SQLDUMPER_ERRORLOG.log
Is the high frequency of log files creation (4MB every 5 minutes) the indication of a bigger issue?
Is there any way to set up these logs to be less intrusive, less verbose and more self-cleaning while still reaping the benefits of unattended problems loging?
Thanks,
Philippe
Yes.
You might be having different and potentially more seriouse issues. Creation of SQLDmpr***.mdmp SQLDmpr***.log files is indication of something going wrong in your server.
You should try and contact customer support and report your problems.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Thank you,
The problem was very simple, the login in the QueryLog connection string did not have write access to the logDB.
This was generating all these Dmpr log files. Not a single log was generated since I fixed it last week.
Philippe
|||I split and edited this thread from an unrelated thread on the Flight Recorder to make it easier for people searching the forum to find this information.