How to Enable Logging for SQL Complete

Logging is a standard mechanism used in many software tools to capture detailed information about application behavior, errors, and performance issues. It is particularly useful when diagnosing problems that are difficult to reproduce or analyze in real time.

This article explains how to enable logging specifically for SQL Complete, an add-in for SQL Server Management Studio (SSMS). Enabling logging helps gather diagnostic data for technical support and is compatible with all supported SSMS versions, including those installed via the official ssms installer or the latest SSMS 21 download.

Steps to Enable Logging

1. Start Tracing

1. On the main SSMS panel, navigate to: SQL Complete > Trace > Start Tracing

2. Reproduce the Issue

1. Perform the actions that lead to the issue you are experiencing.
2. This ensures that the trace log will capture relevant diagnostic data.
   

3. Stop Tracing

1. On the SSMS panel, go to: SQL Complete > Trace > Stop Tracing

4. Send the Trace Log to Devart

1. Navigate to: SQL Complete > Trace > Send Trace Log to Devart

5. Submit Your Information

1. Enter your name, email address, and the ticket number provided in your support request (e.g., #12345).

Notes

Logging is safe to use during normal sessions and does not noticeably affect performance. Make sure your SSMS installation, especially if installed using the SSMS 21 download or SSMS installer, is fully up to date for best compatibility with SQL Complete.

Trace logs play a key role in identifying root causes and enabling faster, more accurate support.

• Related Articles

• How to Enable Logging for Source Control and Data Pump for SQL Server

  Logging is essential for capturing detailed information about failures and issues in the program. If reproducing or diagnosing a problem is difficult, logging helps in providing a deeper investigation. This guide applies to the following products: ...

• How to Enable Logging for SSMS Add-ins Without Built-in Logging

  Logging is essential for diagnosing complex issues and capturing technical details that may not be immediately visible through the user interface. When troubleshooting failures or unexpected behavior in SSMS add-ins that do not provide built-in ...

• How to Enable Logging for Studios, Standalone Tools, and MiniTools

  Logging is essential for capturing detailed information about failures and issues within the software. If reproducing or diagnosing a problem is difficult, or if deeper investigation is needed, logging can help gather more information for ...

• dbForge SQL Tools Missing After Installing or Updating SSMS

  When launching SQL Server Management Studio (SSMS) for the first time after installing dbForge SQL Tools, a brief initialization process is expected. This typically takes 1–2 minutes depending on system performance. If the tools—such as SQL ...

• CPU Metrics Not Displayed in dbForge Monitor for SQL Server

  Symptoms When using dbForge Monitor for SQL Server, you may observe that CPU metrics are not displayed for certain active connections. For instance, the CPU usage section might be empty or missing data, as illustrated in the example below: The ...