Re: FGAC

Niall,

In practice I spent some time fixing up a database where this had been done with little thought with regards to the performance implications. To some degree you can mitigate the risk of poor performance by having appropriate indexes on your tables. I certainly would not advocate just turning on FGAC without spending some time thinking about the implications of the where clauses extension. Personally depending on your choice of criteria for FGAC I like the concept of partitioning using the same rules, so that for most users all the data they are permitted to access resides in one partition!

Kind regards,

Fraser McCallum
MVP Oracle Administration
www.brainbench.com

"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message news:3de217f9$0$8507$ed9e5944_at_reading.news.pipex.net...
> "Noodles" <noodles_at_aol.com> wrote in message
> news:20021125064915.27419.00000083_at_mb-ct.aol.com...
> > Make your SQL is tuned perfectly because as you know, FGAC just appends
> the SQL
> > from the "rule".
>
> Its always seemed to me that by doing this (adding silently to the where
> clause) FGAC *if added retrospectively to an application* could screw up
> access paths. Have you found this in practice or not?
>
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
> *****************************************
> Please include version and platform
> and SQL where applicable
> It makes life easier and increases the
> likelihood of a good answer
>
> ******************************************
>
>
Received on Mon Nov 25 2002 - 18:49:12 CST