Deterministic and nondeterministic functions
Applies to: SQL Server Azure SQL Database Azure SQL Managed Instance
Deterministic functions always return the same result any time they're called with a specific set of input values and given the same state of the database. Nondeterministic functions may return different results each time they're called with a specific set of input values even if the database state that they access remains the same. For example, the function AVG always returns the same result given the qualifications stated above, but the GETDATE function, which returns the current datetime value, always returns a different result.
There are several properties of user-defined functions that determine the ability of the SQL Server Database Engine to index the results of the function, either through indexes on computed columns that call the function, or through indexed views that reference the function. The determinism of a function is one such property. For example, a clustered index can't be created on a view if the view references any nondeterministic functions. For more information about the properties of functions, including determinism, see User-Defined Functions.
Deterministic functions must be schema-bound. Use the
SCHEMABINDING clause when creating a deterministic function.
This article identifies the determinism of built-in system functions and the effect on the deterministic property of user-defined functions when it contains a call to extended stored procedures.
Determining if a function is deterministic
You can check whether a function is deterministic by querying the
is_deterministic object property for the function. The example below determines if the function
Sales.CalculateSalesTax is deterministic.
SELECT OBJECTPROPERTY(OBJECT_ID('Sales.CalculateSalesTax'), 'IsDeterministic');
Built-in function determinism
You can't influence the determinism of any built-in function. Each built-in function is deterministic or nondeterministic based on how the function is implemented by SQL Server. For example, specifying an ORDER BY clause in a query doesn't change the determinism of a function that is used in that query.
All of the string built-in functions are deterministic, except for FORMAT. For a list of these functions, see String Functions (Transact-SQL).
The following built-in functions from categories of built-in functions other than string functions are always deterministic.
The following functions aren't always deterministic, but can be used in indexed views or indexes on computed columns when they're specified in a deterministic manner.
|all aggregate functions||All aggregate functions are deterministic unless they're specified with the OVER and ORDER BY clauses. For a list of these functions, see Aggregate Functions (Transact-SQL).|
|CAST||Deterministic unless used with datetime, smalldatetime, or sql_variant.|
|CONVERT||Deterministic unless one of these conditions exists:
Source type is sql_variant.
Target type is sql_variant and its source type is nondeterministic.
Source or target type is datetime or smalldatetime, the other source or target type is a character string, and a nondeterministic style is specified. To be deterministic, the style parameter must be a constant. Additionally, styles less than or equal to 100 are nondeterministic, except for styles 20 and 21. Styles greater than 100 are deterministic, except for styles 106, 107, 109 and 113.
|CHECKSUM||Deterministic, except for CHECKSUM(*).|
|ISDATE||Deterministic only if used with the CONVERT function, the CONVERT style parameter is specified and style is not equal to 0, 100, 9, or 109.|
|RAND||RAND is deterministic only when a seed parameter is specified.|
All the configuration, cursor, metadata, security, and system statistical functions are nondeterministic. You can see a list of these functions.
The following built-in functions from other categories are always nondeterministic.
- AT TIME ZONE
- NEXT VALUE FOR
Call extended stored procedures from functions
Functions that call extended stored procedures are nondeterministic, because the extended stored procedures can cause side effects on the database. Side effects are changes to a global state of the database, such as an update to a table, or to an external resource, such as a file or the network; for example, modifying a file or sending an e-mail message. Don't rely on returning a consistent result set when executing an extended stored procedure from a user-defined function. User-defined functions that create side effects on the database aren't recommended.
When called from inside a function, the extended stored procedure can't return result sets to the client. Any Open Data Services API that returns result sets to the client, has a return code of FAIL.
The extended stored procedure can connect back to SQL Server. However, the procedure can't join the same transaction as the original function that invoked the extended stored procedure.
Similar to invocations from a batch or stored procedure, the extended stored procedure is executed in the context of the Microsoft Windows security account under which SQL Server is running. The owner of the extended stored procedure should consider the permissions of this security context, when granting permissions to other users to execute the procedure.
Submit and view feedback for