Re: Database Design Best Practice help

From: Tim Gorman <tim_at_evdbt.com>
Date: Tue, 29 Jan 2013 15:42:42 -0700
Message-ID: <51085062.2050802_at_evdbt.com>

One additional thought about consolidating logical entities into a single physical entity -- perhaps the problem becomes more clear if you take the idea all the way to absurdium?

Here is an account of a time when that happened (http://www.simple-talk.com/opinion/opinion-pieces/bad-carma/) along with supplementary commentary on TheDailyWTF (http://forums.thedailywtf.com/forums/p/4166/96314.aspx#96314).

On 1/29/2013 2:38 AM, Sayan Sergeevich Malakshinov wrote:
> Toon Koppelaars wrote,on my timestamp of 28/01/2013 8:13 PM:
>> Just create a union-all view on top of those hundred tables, and write a
>> couple of instead-of triggers to deal with inserts/updates/deletes. Then
>> have your "controller" based on top of this view.
> Unfortunately the views like that increases the chance to get inefficient
> plan, especially when client dynamically build queries with many joins of
> views with big number of tables, even if we increase
> "_optimizer_max_permutations"
>
> Best regards,
> Sayan Malakshinov
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Tue Jan 29 2013 - 23:42:42 CET