v.2.0


New Features List Overview

The following is an overview of the main features and enhancements planned for our next release.  Since the final cut has not been released to manufacturing (RTM), this list may not be final, and additional features and enhancements may be added.  

The best thing of all about these new features, are that they will be part of SQLCentric's core module at no extra cost - FREE!   All users will be eligible for free upgrade.  So, keep watch for our announcement as we approach our release date.

SQLCentric will add two new optional status counters that will monitor the performance of your SQL Servers.  This means the user has the ability to turn them on and off as desired.

The SQLCentric historical reporting and quick reports module, will give the user in-depth reporting capability on the state of their SQL Server infrastructure

Efficiency and Performance


Details

         BCH (Buffer Cache Hit Ratio) Monitor

As you know one of the most important things that SQL Server uses, is memory.  Because reading from the cache is less expensive than reading from disk, you want this percentage to be high.  So, we have added the BCH (Buffer Cache Hit Ratio) Monitor!  Here, the user can set the sampling interval as well as the alert threshold.  For example, if the BCH is consistently below 90% for 5 consecutive samples, you may need to add more memory.

Drill down on the MCache page, and see exactly how much memory is being used by SQL Server, and statistical details on your Buffer and Procedure Cache.

 

          Monitor blocked processes

Another vital status to know is what exactly is going on internal to the SQL Servers' system processes.  One of the reasons for poor performance is blocked processes.  A blocked process is a process that requests a lock, but waits for a competing lock to be released by another process. A high number of blocked processes can cause poor performance due to transaction delays. 

SQLCentric now has the ability to monitor blocked processes, and alert the user to which spid is being blocked and by which spid.  Drill-down to the SysProc page, and you will see all the blocked processes and the TSQL of the lead blocker causing the contention, at the time it was detected.

In addition, you will see the real-time processes of all your SQL Servers. The fantastic new process_monitor will identify the troublemakers causing poor performance, and allow the user to set the wait-time threshold - the maximum amount of time a process should wait, until an alert is generated.

 

          Max Job Intel-Alerts

One of the things we struggled with is to somehow limit the number of job alerts generated, without degrading the integrity of the monitoring system. If a failure is detected an alert will be sent. Now, we have decided to introduce some intelligence into the job alert system:

Max Job Alerts will not only allow the user to set the number of times to be alerted for a particular failed job; it will then reset the alert for the following run time of the job.  On the main status and group page views, a yellow warning light will appear for a job that has met the max job alert threshold, but is still detected as a failure.  

 

        SQLCentric Scheduler

To make the scheduling option more readily available to the user, the SQLCentric admin module interface will manage the implementation of the schedule.  Here you will be able to set the desired runtime schedule, manually run SQLCentric, and view the current status of the runtime executables.

 

        Historical Run-Time Reporting and trend analysis

For historical reporting, the user will be able to select their servers, statistical measures, and date parameters, to generate trend analysis output based on the run-time of the SQLCentric monitoring system - with limited graphing capability

 

        Quick Reports

Quick reports will let the users generate a real-time snapshot of active monitored servers, for such things as server uptime, sql uptime, sql jobs, etc