Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
V0089
The specification states the following:
-
Subclause 6.4, "<value specification> and <target specification>": <value specification> ::= <literal> | <general value specification> <unsigned value specification> ::= <unsigned literal> | <general value specification> <general value specification> ::= <host parameter specification> | <SQL parameter reference> | <dynamic parameter specification> | <embedded variable specification> | <current collation specification> | CURRENT_CATALOG | CURRENT_DEFAULT_TRANSFORM_GROUP | CURRENT_PATH | CURRENT_ROLE | CURRENT_SCHEMA | CURRENT_TRANSFORM_GROUP_FOR_TYPE <path-resolved user-defined type name> | CURRENT_USER | SESSION_USER | SYSTEM_USER | USER | VALUE ... Conformance Rules Without Feature F321, "User authorization", conforming SQL language shall not contain a <general value specification> that contains CURRENT_USER, SYSTEM_USER, or SESSION_USER. NOTE — Although CURRENT_USER and USER are semantically the same, without Feature F321, "User authorization", CURRENT_USER shall be specified as USER. Subclause 11.5, "<default clause>": <default clause> ::= DEFAULT <default option> <default option> ::= <literal> | <datetime value function> | USER | CURRENT_USER | CURRENT_ROLE | SESSION_USER | SYSTEM_USER | CURRENT_CATALOG | CURRENT_SCHEMA | CURRENT_PATH | <implicitly typed value specification> ... Conformance Rules Without Feature F321, "User authorization", conforming SQL language shall not contain a <default option> that contains CURRENT_USER, SESSION_USER, or SYSTEM_USER. NOTE — Although CURRENT_USER and USER are semantically the same, without Feature F321, "User authorization", CURRENT_USER shall be specified as USER. Subclause 19.2, "<set session user identifier statement>": <set session user identifier statement> ::= SET SESSION AUTHORIZATION <value specification> ... Conformance Rules Without Feature F321, "User authorization", conforming SQL language shall not contain a <set session user identifier statement>.
Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2012 vary as follows:
Transact-SQL partially supports this feature. Transact-SQL supports the CURRENT_USER, SESSION_USER, and SYSTEM_USER functions, but does not support a SET SESSION AUTHORIZATION statement.