Re: "Copying" PF-DTA to client via RDi's "Make Available Offline" generates a .OAR file

I understand the XY problem. In this particular case, I had the sense that
it doesn't matter a whole lot to present a "best practices" assessment; it
might be seen more an an insult than just presenting the actual fact that I
*can* actually access i data on the Windows client.

Apparently, this did the job. As of a few minutes ago, I can now use the
client-side tools to query i data.

- Dan

On Wed, Mar 18, 2015 at 12:24 PM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Wed, Mar 18, 2015 at 11:27 AM, Dan <dan27649@xxxxxxxxx> wrote:

The point of the exercise was

And you couldn't have led with that? ;)

Have you heard of the XY problem?

to demonstrate to my manager that, whoever in
the organization (likely an auditor) put the clamp on using any dev-box
database function in Data Studio, Navigator, SQuirreL, Excel, or

basically

any ODBC/JDBC tool we have here, for the express purpose of keeping our
very sensitive data secure, failed to understand that any developer with

a

green screen can copy/paste this sensitive data into a client side file

and

make off with it.

I definitely sympathize and empathize. It's frustrating to have
roadblocks put in your path, making legitimate use more difficult, yet
not providing much if any protection against illegitimate use.

Maybe it's useful to ask: What have others done in this situation? Has
trying to build a case helped? Or has that been viewed as
confrontational and just made the relationship worse? Are there any
"industry best practices" to draw upon here? I know some organizations
are more receptive to evidence from "industry experts" rather than
from within the organization. And the very fact that there is high
variability among different organizations also makes this a difficult
line of inquiry. But some of the folks here have a ridiculous amount
of experience, and their accumulated wisdom may be helpful.