Jim Lawrence
jlawrenc1 at shaw.ca
Sat Jul 19 22:07:24 CDT 2008
Hi Arthur: I would try and keep it as simple as possible as there can be tremendous over-head with this direction as well as some very complex class-like inheritance and reciprocal loops that can come back to bite. I do not have much experience with MS SQL and Views but I am familiar with apps such as Cognos and Discoverer, both Oracle products that are built on top of views on top of views. These programs are created to make managers feel that they can easily generate any reports but never have I seen products that can grind Oracle Enterprise, with 'state-of-the-art' hardware, to its knees faster or actually freeze a site all-together. After all that is said, it should be safe in the hands of a good IT guy, like yourself but definitely be judicious. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Friday, July 18, 2008 11:27 AM To: Discussion concerning MS SQL Server Subject: [dba-SQLServer] Views on Views Does anyone have opinions on the merits or weaknesses of building a view that uses a view, as opposed to the underlying table(s)? In my current project I have found a couple of instances of views depending on other views, and in one case I found a view that depends on three other views. TIA, Arthur _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com