While it's common to externalize end-user visible text, it's a little less common to externalize SQL. But if your application is well structured, SQL should be limited to a set of readily identifiable modules.

But then how do you answer the type of questions I mentioned? Ie, what types of queries, what tables are they querying. Also, when you have > 1000 queries (and queries can be quite large), they take up memory space and should be externalized. I list all the motivations for SQL::Catalog in its docs. Kind of in a hurry now...

Carter's compass: I know I'm on the right track when by deleting something, I'm adding functionality