Re: OT: Validation of end-user reports

From: Freek D'Hooge <freek.dhooge_at_gmail.com>
Date: Wed, 19 Feb 2014 20:58:14 +0100
Message-ID: <1392839894.26854.10.camel_at_dhoogfr-lpt1>



Jeffrey,

My point would be, that if you don't trust the user to create accurate reports, he/she should not be allowed to create reports... It is of course good practice to verify a new report for accuracy, but other then specifying guidelines there is not really you can do. It's the responsibility of the user to actually follow them.

Kind regards,

-- 
Freek D'Hooge
Exitas NV
Senior Oracle DBA
email: freek.dhooge_at_exitas.be
tel +32(03) 443 12 38
http://www.exitas.be 

On wo, 2014-02-19 at 11:31 -0500, Jeffrey Beckstrom wrote:


> I am referring to the validity of the data being reported. In a
> report developed by IT, results are checked for accuracy. For an
> end-user developed report, what are some ways to force the user to
> verify the information they are getting is accurate. We do not want
> decisions being made from bad reporting.
>
> >>> Maris Elsins <elmaris_at_gmail.com> 2/19/14 10:41 AM >>>
>
> Hi Jeffrey,
>
>
>
> What do you mean with "the integrity of the user's reports"?
> If you're referencing to performance impact (to make sure users don't
> kill the system by running huge reports that never complete) We have
> partially addressed this by implementing the resource manager plan to
> limit the number of total active sessions for users connection, the
> degree of parallelism and max amount of CPU % they can utilize. And I
> say "partially" because we're not able to control how much IO they
> cause. no Exadata here ;(
>
>
> ---
>
> Maris Elsins
> _at_MarisElsins
> www.facebook.com/maris.elsins
>
-- http://www.freelists.org/webpage/oracle-l
Received on Wed Feb 19 2014 - 20:58:14 CET

Original text of this message