Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mem_Stats.sql and PerfStats.sql both get exact query #180

Open
gambit9009 opened this issue Jul 1, 2022 · 1 comment
Open

Mem_Stats.sql and PerfStats.sql both get exact query #180

gambit9009 opened this issue Jul 1, 2022 · 1 comment
Assignees
Labels
sqllogscout consider if should also be added to LogScout wave 2 consider this issue for next wave of fixes

Comments

@gambit9009
Copy link
Contributor

gambit9009 commented Jul 1, 2022

Do you want to request a feature or report a bug?
Clean up

What is the current behavior?
Same query running in 2 places. If you get SQL Server Perf Stats and SQL Memory Error. We create and exec sp_mem_stats_grants and sp_mem_stats_grants_mem_script. This sp can have a high mem grant itself.

What is the expected behavior?
Consider only collecting it in one place. Do we need it in both? Are those likely to add SQL Mem Error already going to get SQL Perf Stats?

Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
All versions

@gambit9009 gambit9009 added sqllogscout consider if should also be added to LogScout wave 2 consider this issue for next wave of fixes labels Jul 1, 2022
@gambit9009
Copy link
Contributor Author

May want to file separate issues or maybe a single generic one to compare our different .sql and see where we are getting the same info more than once.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sqllogscout consider if should also be added to LogScout wave 2 consider this issue for next wave of fixes
Projects
None yet
Development

No branches or pull requests

2 participants