Re: Design Question
- From: Jared Still <jkstill@xxxxxxxxx>
- To: robertgfreeman@xxxxxxxxx
- Date: Fri, 16 Oct 2009 14:41:12 -0700
On Fri, Oct 16, 2009 at 2:25 PM, Robert Freeman <robertgfreeman@xxxxxxxxx>wrote:
> ...
> One thing I've found is that the *more* codesets you have, the more complex
> the queries can get. The more complex a query gets, the more difficult it
> becomes to tune. I had a model a couple of years ago with some very complex
> security rules. Each rule really translated into it's own codeset table.
> Also, because of the complexity of the security rules, SQL had to be
> dynamically generated based on various contexts (what a mess!!). It involved
> lots of sub-queries, etc. Performance was a bear for a number of reasons.
>
>
Another approach to that was one advocated by Gurry and Corrigan in
Oracle Performance Tuning (O'Reilly 1996) is to combine multiple lookup
tables into a single table.
IIRC another column was added to indicate what the codes were used for.
That approach may be useful, and as usual, YMMV and it requires testing.
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Oracle Blog: http://jkstill.blogspot.com
Home Page: http://jaredstill.com
Other related posts:
