MIS 605 Topic 8 DQ 1

Topic 8 DQ 1 In theory, how complex could a View statement get? Discuss whether there would be an advantage to chain multiple views under another view. Where does it stop? Explain the possibilities, and support your ideas with specific examples. The complexity is exponential with each addition of each field. Careful attention needs to be made for each line so as not make minute errors, especially with the addition of aliases. Perhaps, experience mitigates the ease or complexity (subjective), however, for novices, this could be a very perplexing exercise to perform and/or understand. As with the previous DQ, I felt it necessary to define a View statement. Views are condensed queries that can be referenced anywhere else in the database. Thus, the code can be maintained and reused elsewhere. When designing views, the DBA needs a clear understanding of the view’s “purpose, the scenario that it fulfills, where the data is located, and the security context under which it will execute”. This in turn, dictates the type of view and how it will provide the most benefit in solving the purpose. As with most things, the theory of diminishing returns rules. Adding more and more information to the view’s output or report simply becomes noise.