Skip to content

SQL LogScout v6.26.01.27

Latest
Latest

Choose a tag to compare

View all tags
@JamesFerebee JamesFerebee released this 05 Feb 17:38
v6.26.01.27
ce4d727
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Download

Scroll down to the bottom of this page and find the Assets section. Expand it and select SQL_LogScout_v6.26.01.27_Signed_2.zip to download it

Verify downloaded file:

You can verify the download by computing the hash of the SQL_LogScout_v6.26.01.27_Signed_2.zip file, using this command:

certutil -hashfile SQL_LogScout_v6.26.01.27_Signed_2.zip SHA512

Compare to this:
3bdf2be7d9aeb854d951a362e0d672a6e4c06a3a5db77dc751f41339e6ff5ff9a5066bca8c402b9d1837e4fd8f209e8184226465d2925cede05668c5c5acc29a

Known Issue(s) in this release

No known issues in this release.

Enhancements

  • Added support for SQL Server 2025.  
  • Introduced the AdditionalOptionsEnabled parameter and corresponding GUI options to support scenarios:
    • NoClusterLogs  
    • TrackCausality  
    • RedoTasksPerfStats  
    • FullTextSearchLogs  
  • Included sys.dm_db_xtp_checkpoint_files DMV data in the Memory scenario.  
  • Moved Full-Text collection out of the Basic scenario into AdditionalOptionsEnabled, with expanded Full-Text logging.  
  • Added the default SQL Server trace (.trc) to the Basic scenario.  
  • Added sqlsetup.log (unattended setup log) to the Setup scenario.  
  • Added UCS Flow Control Extended Event to the AlwaysOn scenario.  
  • Added a collection header to the SQL Assessment API collector.  
  • Added Database Mail information to the README.  
  • Enabled running LogScout directly from File Explorer using “Run as administrator”.  
  • Added collection of sys.dm_os_memory_health_history in the Basic scenario.  
  • Implemented dynamic lookup and use of the highest available bcp.exe version.  
  • Enhanced disk information collection to retrieve mount point details from volumes.  
  • Reformatted RunningDrivers collection output into a table layout.

Fixes

  • Corrected SQL Assessment API import-module behavior.  
  • Fixed instance discovery when running LogScout on a Windows Server node that is part of a WSFC but not an eligible owner of the SQL Server resource—clustered instances will no longer appear as valid collection sources.  
  • Updated Service Broker script to verify database readability before execution.  
  • Resolved an infinite loop caused by failures querying database-scoped configurations.  
  • Prevented collection of cluster registry keys for read-scale (clusterless) Availability Groups in the AlwaysOn scenario.  
  • Corrected msrepl_commands logic in the Replication scenario.  
  • Fixed issues affecting basic and nobasic behavior in the Basic scenario.  
  • Corrected date conversion in the tempdb_and_tran_analysis collection.  
  • Eliminated duplicate columns in sysaltfiles.  
  • Fixed duplicated MiscDiagInfo when using -nobasic.  
  • Resolved issues collecting data for Distributed AGs in the AlwaysOn scenario.  
  • Removed redundant sys.certificates collections.  
  • Fixed tempdb_and_tran_analysis script behavior to stop unnecessary retries, prevent memory growth, eliminate excessive logging, and introduce a delay to avoid constant retry cycles.  
  • Removed an unnecessary "%" character in memory_workingset_trimming output.  
  • Corrected cluster service health lookup for non‑English servers.  
  • Updated Basic scenario fsutil handling to properly display long descriptions and skip CD-ROM sectorinfo output.
  • Improved loading of logging module to prevent errors during startup.
  • Correction to change tracking output in basic scenario.

What's Changed

  • Release 6.26.01.27 in #27

Re-release Info

File Hash

If you previously downloaded the original release for this version, you can compare the file hash using the below command and output.

certutil -hashfile SQL_LogScout_6.26.01.27_Signed.zip SHA512

76cefb1679a3453fb2e3d777080dac1f339e033a1d4f14fad5700da725479227e2a1f61a6b83cef2f757fdf1977e29495249d91299e47d9b91a4c4f64e770067

Previous Known Issue 1 - Certificate chain trust issue

Resolution:

The known issue below was resolved in SQL_LogScout_6.26.01.27_Signed_2 which you can download in the assets of this release.

Symptom:

When running LogScout, you may observe the following error:
"A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider."

Cause:

SQL_LogScout was signed with a certificate that is different than previous versions, where the root certificate may not be trusted on all machines.

Mitigation(s):

Option 1: Use the previous version of SQL_LogScout. https://github.com/microsoft/SQL_LogScout/releases/tag/v6.25.04.25

OR

Option 2: Use ExecutionPolicy to bypass the certificate issue.

You can use Set-ExecutionPolicy to a value of bypass to ignore the error and not check similar to below. However, do this at your own risk.

powershell.exe -ExecutionPolicy Bypass -File .\SQL_LogScout.ps1
Assets 3
Loading