4 ms·
We had a utility I wrote at one of the places I worked where you ran it against the database and it showed you all of the query plans running. It was easy with
by protomyth 11y ago
We had a utility I wrote at one of the places I worked where you ran it against the database and it showed you all of the query plans running. It was easy with 15 seconds to see some non-indexed query and what was executing it. We used to run it after new version deployments to see if we had query problems. Tooling is very important.
- shazow 11y agoThat sounds really handy, any chance it's publicly available or you can make it so?
- protomyth 11y agoNo, I couldn't release it due to not having the source or being in a position to ask permission. It was for Sybase but the same thing can be achieved in MS SQL by reading some system tables. It really wasn't that hard of a thing to write.
- perlgeek 11y agoAs a stopgap solution, enabling the slow query log can also be very helpful.
- protomyth 11y agoYep. A lot of databases have some form of system tables that can tell you a lot about a running system with just some queries. I know Sybase and MS SQL server have the tables to find all the current queries and what they are doing. Ingress had a neat graph (seeing FSM should illicit a panic in most DBAs) and a log monitor. Read up on what is part of the database and write some tools.