You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you want to request a feature or report a bug? New Feature
What is the current behavior? When user launches Diag Manager they can perform the required configuration and generate the PSSDIAG package to perform the log collection.
**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem **
What is the expected behavior? When user launches Diag Manager, provide a lite prompt to educate them about using SQL LogScout instead of PSSDIAG. Same with the PSSDIAG capture, at the end, can we print a line on the console window to educate users about using SQL LogScout next time.
Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug? New Feature
What is the current behavior? When user launches Diag Manager they can perform the required configuration and generate the PSSDIAG package to perform the log collection.
**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem **
What is the expected behavior? When user launches Diag Manager, provide a lite prompt to educate them about using SQL LogScout instead of PSSDIAG. Same with the PSSDIAG capture, at the end, can we print a line on the console window to educate users about using SQL LogScout next time.
Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
The text was updated successfully, but these errors were encountered: