What's new at SQLGrease?

We are continually working to improve SQLGrease. Check back often to see what features we recently added.

Latest Updates

SQL Server 2017 Supported

SQLGrease is now officially supported for use on SQL Server 2017.

Query Memory Analysis Added

A new feature now allows you to see what queries have memory grants. This feature is useful for diagnosing memory pressure issues especially in the case of RESOURCE_SEMAPHORE waits. With this feature you can visualize the memory footprint of your most resource intense queries. This view is overlayed with a chart of memory grants pending.

Database elapsed time chart added

A new chart was added which lets you see which databases are generating the most workload on an instance. This allows you to quickly identify which database to drill into and research further. This is extremely helpful in multi-tenant environments where a large number of databases are hosted on a single instance.

Missing index check added to plan warning event source

The plan warning event source now has an option for creating events when new execution plans collected contain missing indexes.

Plan Warning Event Source

SQLGrease now has a plan warning event source. This can be used to notify you of when execution plans with missing joins, implicit conversions, or columns with missing statistics are detected.

Color coding of wait events for Execution Snapshots

As a visual queue, wait events are now color coded in executing query snapshots. This helps to more clearly identify when an executing session is in a wait event and which wait event is affecting performance.

Preconfigured Rule Sets Added

Two preconfigured event rule sets were added.

  • CPU Pressure (Threadpool)
  • Internal memory pressure

The CPU Pressure event rule set is triggered by queries experiencing the THREADPOOL wait event. The Internal memory pressure rule set is triggered by queries experiencing the RESOURCE_SEMAPHORE or RESOURCE_SEMAPHORE_QUERY_COMPILE wait events.

Page Life Expectancy Event Added

You can now configure events based on page life expectancy (PLE).

Competitive Pricing

SQLGrease is now offering competitive pricing discounts. Click here for more info

Query Execution Timeout Detection

SQLGrease can now identify the occurence of client side query aborts. These typically occur when a client hits its max query wait time (most platforms are set to 30 seconds by default). At the moment this feature is only available for SQL 2012 and later versions.

FREE Trial, no credit card needed!

FREE! We now have a free 7 day trial plan, no credit card required.

DTU Estimator

The DTU estimator allows you to see what the estimated DTU and service level will be required when you migrate your workload to Azure SQL Database.

Parallel Query Waits

The parallel query wait feature allows you to view beyond CXPACKET wait events, and view the underlying waits encountered by the parallel tasks. This appears as a new chart in the Query Detail view.

Average Row Count/Execution Chart

A new chart was added to the Query Detail view. This chart allows you to view average row count per execution over time.

Average Elapsed Time/Execution Plan Chart

A new chart was added to the Query Detail view. This chart allows you to view the average elapsed time for each execution plan over time.

Execution Plan Change Event Source

A new event source was added for execution plan changes. This can be used to configure events based upon changes in execution plans and the resulting change in elapsed times, IO's, CPU time, or rows processed.

Amazon RDS Support

Amazon RDS SQL Server instances are now supported in SQLGrease.

Execution Plan Warnings

The SQL Server optimizer will generate execution plan warnings whenever it generates execution plans that seem problematic. SQLGrease will detect these and display these in the Query Detail view under the Execution Plan tab.

Deadlock Monitoring

SQLGrease now includes a robust deadlock monitoring feature which not only collects deadlock information, but it also groups similar deadlocks together in order to quickly see which deadlocks should be fixed first.