Skip to content

PSBlitz v4.5.0 - some fail-safes for instances with lots of databases

Latest
Compare
Choose a tag to compare
@VladDBA VladDBA released this 20 Nov 01:14
b97760c

What's new:

Behavior changes

Issue #279
Starting with this release, if an instance-wide check is being done on an instance with 50 or more databases, PSBlitz will automatically limit the following checks to the database that appears the most in the data returned by the cache related checks:

  • Index Summary
  • Index Usage Details
  • (Detailed) Index Diagnosis

New parameter

The -MaxUsrDBs parameter was introduced to control the cutoff for the behavior change described above. The default is 50, but only change the value if most of those databases don't have too many tables and/or indexes, or you've opted to output to HTML and have enough RAM for PS to handle the excess data. Note that PSBlitz will limit the Index Usage and Index Diagnostics outputs to 30k records if more rows are returned.

New cache related checks

Issues #115, #277
Duplicates and query hash will provide data about queries with duplicate plans and queries with single use plans.

More info added to the "Instance Info" and "Database Info" report pages

Instance Info

Issue #282
Now shows the buffer usage in GB in the "Resource Info" section.

Database Info

Issue #280
Now shows the amount of cached data in GB and the percent of buffer usage on a per-database basis in the "Database Info" section

Additional info captured in the execution log

Issue #278
The execution log now makes a note of the type of authentication used (not the credentials or anything like that) either SQL or trusted - this is purely for debugging purposes.

More info

  • Dev - 3AM PR - aka some people really live with 100+ databases on one instance by @VladDBA in #284

Full Changelog: v4.4.1...v4.5.0