Store complex queries — Views can be used to store complex queries. Rename Columns — Views can also be used to rename the columns without affecting the base tables provided the number of columns in view must match the number of columns specified in select statement.
Thus, renaming helps to to hide the names of the columns of the base tables. Multiple view facility — Different views can be created on the same table for different users. This article is contributed by Harsh Agarwal. If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please write comments if you find anything incorrect, or you want to share more information about the topic discussed above. Skip to content. Change Language. Related Articles. Values are True and False. Encrypted Indicates whether the view is encrypted. Quoted identifier Indicates if the object was created with the quoted identifier option. Schema bound Indicates whether the view is schema-bound. In Object Explorer , expand the database that contains the view to which you want to view the properties, and then expand the Views folder.
Right-click the view of which you want to view the properties and select Design. Bind to Schema Prevents users from modifying the underlying objects that contribute to this view in any way that would invalidate the view definition. Deterministic Shows whether the data type of the selected column can be determined with certainty. Distinct Values Specifies that the query will filter out duplicates in the view.
This option is useful when you are using only some of the columns from a table and those columns might contain duplicate values, or when the process of joining two or more tables produces duplicate rows in the result set. Output All Columns Shows whether all columns are returned by the selected view. This is set at the time the view is created.
In the following query, we want to get only two columns name and contract type from the view. Rerun the select statement to get records from VIEW. It should display the new column as well in the output.
We still get the same output, and it does not contain the newly added column. We can see the City column in the output.
In the previous example, we modify the SQL table to add a new column. Suppose in the production instance, and you have a view in the application. You are not aware of the changes in the table design for the new column.
We do not want any changes to be made in the tables being used in the VIEW. Names must be in a two-part format, and an object cannot reference itself.
In my query, I used a three-part object name in the format [DBName. We can use the two-part name as per the following query. We need to drop the VIEW definition itself along with other dependencies on that table before making a change to the existing table schema. If we do not want users to view the definition, we can encrypt it.
Next Page. Previous Page Print Page. Save Close. Dashboard Logout.
0コメント