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.

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

sp_BlitzCache (and probably BQS): Database trigger names don't resolve #1576

Closed
BlitzErik opened this issue May 14, 2018 · 2 comments
Closed

sp_BlitzCache (and probably BQS): Database trigger names don't resolve #1576

BlitzErik opened this issue May 14, 2018 · 2 comments
Assignees
@BlitzErik
Labels
bug sp_BlitzCache sp_BlitzQueryStore

Comments

@BlitzErik
Copy link
Contributor

image

BOO! BOO THIS MAN!
@BlitzErik BlitzErik self-assigned this May 14, 2018
@BlitzErik
Copy link
Contributor Author

This is weird.

image

@BlitzErik
Copy link
Contributor Author

What sucks about this is that the only way to get the trigger info is from sys.triggers, which is per-database. I don't think it's worth writing a lot of extra code to get this. I'm fine with it as a known limitation.

We don't see folks using database triggers all that often. Even when we do, they're hardly the worst thing in the plan cache.

We'll just have to leave the nice people of the world who use this thing to look at the query text to identify database triggers.

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

@BlitzErik BlitzErik

Labels
bug sp_BlitzCache sp_BlitzQueryStore
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BlitzErik