Teradata Views created on top of Views

Database

Teradata Views created on top of Views

Hi Guys,

I have a question regarding Teradata Views that are created on top of other Teradata Views.

Architecture is as follow: first/base level is Teradata tables, second layer is Teradata Views that are created on top of tables with one to one column mapping, third layer is also teradata views that are created on top of second layer views however have logic in them i.e. combining two or more then two second layer Views. Reporting tool access Views from third layer...

My question is if accessing Teradata Views that are created on top of Views would cause any performance decrease as compare to accessing Views that are created on top of tables. what are the pros and cons to this approach? 

thanks 

Tags (1)
1 REPLY

Re: Teradata Views created on top of Views

Shouldn't be an issue as long as you don't go to deep in your layers of views.  Hopefully query re-write will fold the views and only access the actual tables that are referenced in the select.  I believe the preferred approach is to always access a view in order to take advantage of the 'lock row for access'.