Archives of the TeradataForum
Message Posted: Fri, 14 Jan 2011 @ 13:32:37 GMT
Hopefully a simple one to answer ...
We're considering creating another Database that holds every View across every Table in all our Application Table Databases. The idea is to have one central repository of information (i.e. Views), whereby developers can go to in order to find what they want or, if it's not there, to know that it's not been defined in some other obscure area.
My question, is there any performance overhead in accessing Views from a Database, which itself contains potentially thousands of View entries?
In addition, is there any overhead in defining the View as (SELECT * FROM A_TABLE) as opposed to naming specific Columns i.e. SELECT COL1, COL2, etc FROM A_TABLE ?
Lastly, when a View is compiled by using the SELECT * type construct, any new Columns subsequently added to the Table are not , I would assume, picked up in the definition - right ?
Before we press forwards with our architectural document, I wanted to get any feedback of a positive, negative or 'watch out for' nature.
Regards and thank you
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|