miniDBA offers a detailed view into a SQL Server's performance, from instance level all the way through databases and users, down to individual batches of T-SQL.
It will help you tactically diagnose issues when they arise and also allow you to strategically tune a server to prolong the hardware's lifetime.
miniDBA client is a stand alone desktop client, not dependant on any services, agents or repository databases running on any other computers. This enables you to connect to SQL Servers whenever you like, without waiting for administrators to setup monitoring software for you.
miniDBA Server can optionally be installed - it takes care of its own data logging and has no dependancies on logging databases or other services or agents
No - miniDBA gives you other performance metrics such as server memory, non sql instance related CPU load, CPU performance by core, logical and physical disk performance.
miniDBA Client connects to Azure SQL Database and Analysis Services instances, both multi-dimensional and tabular.
You can quickly point miniDBA at any SQL Server instance to enable you to identify why T-SQL you are dependant on is running slowly. Regardless of the language you develop code in, there comes a time when the database slows you down and you rely on an administrator to help you solve the problem. With miniDBA you don't need to wait for them to become available and spend time helping you.
In development environments that include local, development, UAT, and virtual servers, the ability to connect to any of these without worrying about the time and expense of software setup or licensing puts you ahead.
Either use miniDBA to sit in the background and alert you to when things go wrong or use it pro-actively to performance tune a server or database.
Diagnostic healthchecks, realtime dashboards and live data views of waits, runnning SQL, locks, index usage etc gives you what you need you need to home in on any performance problem.
The historic performance data viewer will enable you to make informed strategic descisions and prolong server lifetime.
Yes - you will be able to see database changes over time as well as view all the performance data that miniDBA writes to log files as it works. You can review this historical data in the miniDBA history viewer window.
Using windows or SQL Server authentication the user can use miniDBA to monitor the server as long as they have VIEW SERVER STATE permission.
SA and\or DBO permissions are not required - making miniDBA useable by people outside the usual DBA domain.
miniDBA issues a small lockless sample query against the server which consume less than a single percentage of server CPU, even on very low end hardware.
In testing on a mid range 8 core 3Gh desktop pc running SQL Server 2008 R2 at the default sample rate of 5 seconds it takes 10 instances of miniDBA to break the 1% SQL usage barrier.
On hardware more powerful than this desktop pc, expect to see even less of an effect than this.
On servers earlier than 2012 SP1, entries in the sql server error log will occur every minute "Using dbghelp.dll version 4.0.5". This is a purely informational message of the lowest priority that is issued whenever SQL Server's extended events are queried.
miniDBA does this once per minute to check for deadlocks. The message can be safely ignored or eliminated when upgrading to 2012 SP1.
The lite version is free and only has a single server dashboard, Developer edition has all features apart from alerts and Enterprise edition has all including alerts.
Developer and Enterprise Editions can optionally connect to miniDBA Server.
Only miniDBA Client Enterprise edition can be used to administer miniDBA Server.