Deterministic functions always returns the same output result all the time it is executed for same input values. i.e. ABS, DATEDIFF, ISNULL etc.
Nondeterministic functions may return different results each time they are executed. i.e. NEWID, RAND, @@CPU_BUSY etc. Functions that call extended stored procedures are nondeterministic. User-defined functions that create side effects on the database are not recommended.
Reference : Pinal Dave (https://blog.sqlauthority.com)
Is your SQL Server running slow and you want to speed it up without sharing server credentials? In my Comprehensive Database Performance Health Check, we can work together remotely and resolve your biggest performance troublemakers in less than 4 hours.
Once you learn my business secrets, you will fix the majority of problems in the future.
Have you ever opened any PowerPoint deck when you face SQL Server Performance Tuning emergencies? SQL Server Performance Tuning Practical Workshop is my MOST popular training with no PowerPoint presentations and 100% practical demonstrations.
Essentially I share my business secrets to optimize SQL Server performance.
6 Comments. Leave new
Hello Pinal
can i have more example of non deterministic function which are taking parameters.
i have on doubt?
can we call a non determenistic funtion in our user defined function..if not why?
can we call a non determenistic funtion from our user defined function..if not why?
I’m working on loading data into tables using some stored-procedures as a model for doing so. In one stored-procedure is this variable assignment
SELECT TOP 1 @RowD = RowID FROM NameofTable WHERE ReferenceID = @ReferenceID;
Glancing over it I did not notice anything of significance. Then I put it into practice in the script that is loading data. When testing I immediately saw it was not returning what I was expecting it to return. Based on what the original SP was doing I was expecting it to return the highest ID. But it wasn’t Then I realized there is no ORDER BY clause. To me this is saying the SELECT statement is non-deterministic. When the tests were run the result was the same value, but that value was neither the lowest or highest value.
I just though this is a good example of expecting something but not getting because of a missing ORDER BY clause
select OBJECTPROPERTY(OBJECT_ID(‘dbo.AddNumbers’), ‘IsDeterministic’); return 0. The AddNumbers function simply adds two numbers. it is deterministic function. then why objectproperty function is returning zero instead of one.