ABSTRACT
Often, a database application extracts data from databases, displays data for front-end users, or saves new data or modified data back to the databases. For many interaction-intensive applications, using tables directly will generate frequent table searching and updating that hold back database performance. It is also not secure to allow the front-end users to directly access a database through a database application. The SQL programming unit, view, can be developed to improve the database performance by precollecting the data needed for a database application. A view can be used to carry out calculations, which significantly reduce the database performance if they are done on tables. If database applications directly communicate with views, not tables, this will improve performance and security.
