RE: Would you allow this?

It's just a read-only reporting tool? Is it something like Cognos Impromptu/Powerplay, Oracle Discoverer, Hummingbird BiQuery (or whatever it's called these days)?

These read-only tools are OK to demo against production, although if you have a test/development database to support your production database, that might be a better one for the first try (till you're comfortable with it). What do you mean, it's their database? Is it a database for a third-party vendor, and the same third-party vendor wants to demo their new reporting tool?

If a query goes haywire and eats too many resources, just kill it. If it is read-only, it shouldn't hurt anything or cause corruption. They'll probably need a username/password to connect. Create a read-only user and have them use that. (That's what I've done for our reporting tool). If they're not satisfied with that, and/or want soemthing like system, then you should definitely keep fighting.

HTH,
Sara Wasserman
Eugene, OR
> -----Original Message-----
> From: Lisa_Koivu_at_gelco.com [SMTP:Lisa_Koivu_at_gelco.com]
> Sent: Tuesday, June 13, 2000 9:55 AM
> To: Multiple recipients of list ORACLE-L
> Subject: Would you allow this?
>
> How many of you would allow a vendor to come in and do a demo on a
> PRODUCTION
> DATABASE?
>
> I am being overridden. I am being told to allow it, it's their database
> and if
> they hose it (who knows what this thing is going to do?) it's their
> problem.
> What? It's just a reporting tool, but STILL! I am concerned about it
> starting
> runaway queries and eating up resources reserved for CUSTOMERS.
>
> Can you feel my headache all the way from Minneapolis.... I should just
> take
Received on Tue Jun 13 2000 - 13:58:23 CDT