Share via


2.1.2.105 F771, Connection management

V0141:

The specification states the following:

 Subclause 5.4, "Names and identifiers":
  
 <connection name> ::=
 <simple value specification>
  
 ...
  
 Conformance Rules
  
 Without Feature F771, "Connection management", conforming SQL language shall not contain an explicit <connection name>.
  
 Subclause 13.4, "<SQL procedure statement>":
  
 <SQL connection statement> ::=
 <connect statement>
 | <set connection statement>
 | <disconnect statement>
  
 Subclause 18.1, "<connect statement>":
  
 <connect statement> ::=
 CONNECT TO <connection target>
  
 <connection target> ::=
 <SQL-server name> [ AS <connection name> ] [ USER <connection user name> ]
 | DEFAULT
  
 ...
  
 Conformance Rules
  
 Without Feature F771, "Connection management", conforming SQL language shall not contain a <connect statement>.
  
 Subclause 18.2, "<set connection statement>":
  
 <set connection statement> ::=
 SET CONNECTION <connection object>
  
 <connection object> ::=
 DEFAULT
 | <connection name>
  
 ...
  
 Conformance Rules
  
 Without Feature F771, "Connection management", conforming SQL language shall not contain a <set connection statement>.
  
 Subclause 18.3, "<disconnect statement>":
  
 <disconnect statement> ::=
 DISCONNECT <disconnect object> 
  
 <disconnect object> ::=
 <connection object>
 | ALL
 | CURRENT
  
 ...
  
 Conformance Rules
  
 Without Feature F771, "Connection management", conforming SQL language shall not contain a <disconnect statement>.

Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2012 vary as follows:

Transact-SQL partially supports this feature. Connection management is supported only within embedded SQL programs. See the USE statement [MSDN-USE] for equivalent functionality.