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.

Sign up for GitHub

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

Jump to bottom

If NULL shows up as a database for more than 2/3 of the plan cache records, the switch to run stats and index frag checks is triggered #132

Closed

VladDBA opened this issue Nov 7, 2023 · 0 comments · Fixed by #142

Assignees

Labels

bug

Owner

VladDBA commented Nov 7, 2023

No description provided.

VladDBA self-assigned this

VladDBA added the bug label

VladDBA changed the title ~~Stop triggering stats and index frag checks if NULL database name is returned by the cache checks in more than 1/3~~ Occasionally if NULL shows up as a database for more than 1/3 of the plan cache records, a switch to run stats and index frag checks is triggered

VladDBA changed the title ~~Occasionally if NULL shows up as a database for more than 1/3 of the plan cache records, a switch to run stats and index frag checks is triggered~~ Occasionally if NULL shows up as a database for more than 2/3 of the plan cache records, a switch to run stats and index frag checks is triggered

VladDBA changed the title ~~Occasionally if NULL shows up as a database for more than 2/3 of the plan cache records, a switch to run stats and index frag checks is triggered~~ Occasionally if NULL shows up as a database for more than 2/3 of the plan cache records, the switch to run stats and index frag checks is triggered

VladDBA changed the title ~~Occasionally if NULL shows up as a database for more than 2/3 of the plan cache records, the switch to run stats and index frag checks is triggered~~ If NULL shows up as a database for more than 2/3 of the plan cache records, the switch to run stats and index frag checks is triggered

VladDBA mentioned this issue

Merged

VladDBA closed this as completed in #142

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment