T-SQL Study #01: Create View and Procedure Options

It’s time to work on some goals for 2014. Obtaining a SQL Server certification is something I had planned to pursue last year, but am determined to tackle it this year. The first test is 70-461: Querying Microsoft SQL Server. For each test, I will review the high level objectives, jot down the areas I am weak in, and then blog about it. When I’m finished I will have a collection of study notes and will also have increased my blog post count for this year. That, my friends, is called efficiency 😉

The maiden topic is pretty basic: Reviewing some of the options for creating views and stored procedures.



Notes: A view can be created only in the current database. The CREATE VIEW must be the first statement in a query batch. A view can have a maximum of 1,024 columns.

Binds the view to the underlying objects if references such that no changes are allowed to referenced objects unless you drop or alter the view to not use schema binding.
Encrypts the contents from displaying in sys.syscontents. Also, does not publish with replication.
Presents the column metadata as belonging to the view i.e. masking the base tables. Useful to assist ORM tools from getting confused walking the structure of data returned.
Used when updating data through a view. Forces update statements to follow the criteria set within the underlying SELECT statement. In other words, if an UPDATE causes a row to disappear from the view, the UPDATE fails.



Like with CREATE VIEW, obfuscates the procedure definitiontext. However, the text is viewable by privileged users who can access system tables. Cannot be published with replication.
Specifies the security context under which to execute the procedure.

The current owner of the module (or schema if blank)
Equivalent to EXECUTE AS [user], where the specified user is the person creating or altering the module
The default for all modules except queues. Executes under the context of the person clling the module (duh).
Specifies a specific user. Note: Must be a singleton account i.e. no group, role, or built-in account
Instructions to not cache the query plan. Cannot be published with replication. Used to counteract “parameter-sniffing”. More information: http://technet.microsoft.com/en-us/library/ms190439.aspx
T-SQL Study #01: Create View and Procedure Options