Session 1: Intro - How to run SQL LogScout and collect some logs

Tech/product focus: SQL LogScout tool setup + log collection workflow

Purpose of the series

Videos meant to make it easier to use Microsoft SQL LogScout and collect useful diagnostics.

---

Where to download SQL LogScout

• Easiest (rememberable) link: AKA dot MS slash get SQL log Scout
• Also available from Microsoft’s GitHub releases page: github.com/microsoft/SQL_logScout/releases

The releases page includes the latest version and previous releases.

---

Installation / launch steps (Windows)

1. Download the package (a single ZIP file).
2. Extract the ZIP to a folder.
3. Open Command Prompt and navigate to the extracted folder.

---

Running SQL LogScout (command-line mode)

When starting, the tool detects SQL Server instances running on the system.

Options include:

• GUI mode
• Non-GUI (command line) mode

This tutorial uses non-GUI / command line mode.

---

Scenario selection

LogScout prompts for:

• Using the current directory (default)
• Selecting a troubleshooting scenario

The speaker selects:

• General scenario (entered as 1)
• Additional collection option(s) using numeric flags (entered as +4 and 1+4 shown in subtitles)
• Mentions collecting Always On / latency/data movement related info via Extended Events / Always On health & diagnostics

---

Choosing which SQL Server instance to target

• The tool displays discovered instances.
• The speaker selects index 0 (only one instance present).

---

Starting and stopping diagnostic collection

Collection begins and the screen instructs: “type stop to terminate diagnostic collection.”

Stopping guidance:

• If the issue is reproducible: start collection → reproduce the problem → type stop
• If the issue is already happening: collect while the problem is occurring

---

What gets collected (basic scenario logs)

After typing stop, LogScout shuts down and collects basic scenario logs, including:

• Running processes on the system
• Filter drivers information
• System information
• SQL Server error logs
• System Health / XC event files (as described)
• Cluster logs (because the system is a cluster)
• Windows/Event logs related to clustering (mentioned in context)
• Extended Events (referenced for Always On latency/data movement)

---

Output / where logs are stored

After collection, the tool prints output and shows where logs are saved.

The speaker demonstrates artifacts such as:

• Perfmon file(s)
• Always On health events
• SQL Server error logs
• Filter driver information
• Running processes
• XEvents / basic XEvents (matching the scenario selection)
• Various other generated files

Notes:

• Cluster log collection usually takes ~1–2 minutes.
• Cluster logs are reported as found in a cluster log folder (subtitle shows: “here … cluster logs can be found here”).

---

Overall takeaway from the intro / tutorial

The video provides a step-by-step command-line workflow:

1. Download (link or GitHub releases)
2. Extract ZIP
3. Run in non-GUI mode
4. Select scenario (General + optional extra flags like +4)
5. Pick SQL instance index
6. Start collection, then type stop when ready
7. Review generated diagnostics (error logs, XEvents, perfmon, cluster logs, etc.)

---

Main speaker(s) / source(s)

• Source: Microsoft SQL LogScout (documentation-style tutorial from a presenter)
• Speaker: Unspecified in subtitles (no name given)