SQL Server Historic Data Storage - mini DBA


Legacy Documentation

Desktop And Mini DBA Server

Legacy Documentation Home alerts analysisservicesalerts analysisservicescpu analysisservicesdashboard analysisservicesdatabases analysisservicesio analysisservicessessions azurealerts azuredatabase azuredatabasehealthcheck azureindexes azurelocks azure security azuresessions azuresql azuresqldatabase azuresqldatabasedashboard azuresqldatabases azure sql server dashboard azuretables azurewaits compare performance baseline connections cpu custom sql server alerts database database query performance databases defaulttrace dm exec query statistics xml documentation errorlog files gettingstarted healthcheck database healthcheck sql server history active history blocking history data storage history deadlocks history files history memory history viewer history waits howtoperformancetuneazuresqldatabase how to performance tune sql server how to sql server performance tuning how to sql server query tuning indexes Installation io License Support locks maintenance windows options performance history security server servergettingstarted Server Installation server memory serveroptions serversecurity servertroubleshooting sql database memory sql execution plan sql extended event sessions sql server activity sql server alert configuration sql server alerts sql server database sql server execution plan view sql server index defrag jobs sqlserverindexfragmentation sql server index fragmentation sql server index maintenance sql server live query statistics sqlserverqueryperformance sql server query performance sql server send slack alerts sql server send teams alerts sql server transaction log sql server wait statistics tables tranlog waits webmonitorconfigure webmonitorconnections webmonitorcurrent webmonitorcustom webmonitorenterprise webmonitorgettingstarted webmonitorhistoric webmonitorinstallation webmonitorio webmonitormemory webmonitoroptions webmonitoroverview webmonitorsecurity webmonitorwaits wmi
Mini DBA does not require a back end database of any kind to store data, as the storage is self contained. This reduces potential licensing costs and maintenance overhead of keeping the backing database monitored/de fragmented etc.

Historic data is written to files and stored by server and date. The files default locations are:
  • Mini DBA Desktop: C:\Users\[username]\AppData\Local\miniDBA Desktop\logs
  • Mini DBA Server: C:\ProgramData\miniDBA Server\logs
These locations can be changed in the options for both Mini DBA Desktop and Mini DBA Server. The log files are deleted after 30 days and can be large is size, potentially around 1Gb per day, per server on a busy server.
The large size mostly stems from T-SQL execution plans being stored, which may be extremely large. Not every execution plan is stored as trivial ones may consume a lot of disk space and probably not likely to be interesting. Only T-SQL requests that have been executing for more than 1 second have their execution plans logged.

These log files are transferable between instances of Mini DBA so you can copy them to any Mini DBA Server or Desktop installation and they will be available to read. Note if you are using Mini DBA Server all users will be able to read the logs that it is writing to so it is unlikely you will need to copy any log files to anywhere.