× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. July 2017

Re: Read-only SYSCATALOGS OK?

On 7/20/2017 4:32 PM, Justin Taylor wrote:
Some users have a query tool they want to connect to DB2. When creating a connection, it tries to query QSYS2.SYSCATALOGS. I'm not inclined to allow access, but I don't have any solid reason not to. Am I just being paranoid?

The tool will probably want to know about the rest of the catalogue too.
The catalogue reveals everything about your database. Every schema,
table, view, column, trigger, procedure, and function. That's a lot of
info to give out. It's actually the first thing I look for when I want,
er, access to a system that, um, say another department, well, hasn't
got round to giving me access too. Just yet. Having all those names is
really helpful when it comes to formulating queries that are on-point.

On the other hand, a generic query tool will probably be harder to use
if it can't browse the system, so to speak.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.