Comments on: SQL SERVER – 2005 – Use of Non-deterministic Function in UDF – Find Day Difference Between Any Date and Today http://blog.sqlauthority.com/2007/08/23/sql-server-2005-use-of-non-deterministic-function-in-udf-find-day-difference-between-any-date-and-today/ Notes of a SQL Server MVP and Database Administrator Sat, 21 Nov 2009 05:54:09 +0000 http://wordpress.com/ hourly 1 By: m0thmanUD http://blog.sqlauthority.com/2007/08/23/sql-server-2005-use-of-non-deterministic-function-in-udf-find-day-difference-between-any-date-and-today/#comment-51786 m0thmanUD Mon, 11 May 2009 17:30:32 +0000 http://blog.sqlauthority.com/2007/08/23/sql-server-2005-use-of-non-deterministic-function-in-udf-find-day-difference-between-any-date-and-today/#comment-51786 This is a real pain. I wanted to use RAND() in a UDF I was putting together to generate random URL keys and hit a brick wall with this. I know there's a few workarounds, such as having the RAND in a view, or just using a stored proc instead, but it's a real pain. Just can't understand the logic of banning the RAND function from within a UDF! This is a real pain. I wanted to use RAND() in a UDF I was putting together to generate random URL keys and hit a brick wall with this.

I know there’s a few workarounds, such as having the RAND in a view, or just using a stored proc instead, but it’s a real pain. Just can’t understand the logic of banning the RAND function from within a UDF!

]]> By: Malar http://blog.sqlauthority.com/2007/08/23/sql-server-2005-use-of-non-deterministic-function-in-udf-find-day-difference-between-any-date-and-today/#comment-44573 Malar Sat, 06 Dec 2008 12:28:17 +0000 http://blog.sqlauthority.com/2007/08/23/sql-server-2005-use-of-non-deterministic-function-in-udf-find-day-difference-between-any-date-and-today/#comment-44573 how to change only day part with the day what we want in the date? for example,i need to compute the date(6-dec-08) which is having the day('6' should be changed) part from a table. how to change only day part with the day what we want in the date?
for example,i need to compute the date(6-dec-08) which is having the day(‘6′ should be changed) part from a table.

]]> By: SQL SERVER - Function Property - Deterministic or Non-Deterministic Journey to SQL Authority with Pinal Dave http://blog.sqlauthority.com/2007/08/23/sql-server-2005-use-of-non-deterministic-function-in-udf-find-day-difference-between-any-date-and-today/#comment-38293 SQL SERVER - Function Property - Deterministic or Non-Deterministic Journey to SQL Authority with Pinal Dave Sat, 17 May 2008 09:39:23 +0000 http://blog.sqlauthority.com/2007/08/23/sql-server-2005-use-of-non-deterministic-function-in-udf-find-day-difference-between-any-date-and-today/#comment-38293 [...] SQL SERVER - 2005 - Use of Non-deterministic Function in UDF - Find Day Difference Between Any Date ... You can run following code to determine if function is deterministic or not. [...] [...] SQL SERVER – 2005 – Use of Non-deterministic Function in UDF – Find Day Difference Between Any Date … You can run following code to determine if function is deterministic or not. [...]

]]> By: Chris http://blog.sqlauthority.com/2007/08/23/sql-server-2005-use-of-non-deterministic-function-in-udf-find-day-difference-between-any-date-and-today/#comment-34251 Chris Tue, 11 Mar 2008 14:31:56 +0000 http://blog.sqlauthority.com/2007/08/23/sql-server-2005-use-of-non-deterministic-function-in-udf-find-day-difference-between-any-date-and-today/#comment-34251 So in other words, we're not able to do things we should logically be able to do because of poor design in SQL Server's internals? Yes, heaven forbid a UDF use Rand(), and make subsequent calls to Rand() non-deterministic... Someone as M$ is taking the whole "no side-effects" thing a bit too literally. At least this is a step in the right direction. So in other words, we’re not able to do things we should logically be able to do because of poor design in SQL Server’s internals? Yes, heaven forbid a UDF use Rand(), and make subsequent calls to Rand() non-deterministic…

Someone as M$ is taking the whole “no side-effects” thing a bit too literally. At least this is a step in the right direction.

]]> By: Simon http://blog.sqlauthority.com/2007/08/23/sql-server-2005-use-of-non-deterministic-function-in-udf-find-day-difference-between-any-date-and-today/#comment-9107 Simon Thu, 23 Aug 2007 19:06:29 +0000 http://blog.sqlauthority.com/2007/08/23/sql-server-2005-use-of-non-deterministic-function-in-udf-find-day-difference-between-any-date-and-today/#comment-9107 SQL Server 2005 has allowed some of the non-deterministic functions that were not allowed in 2000. In 2005 you can now use CURRENT_TIMESTAMP @@MAX_CONNECTIONS GET_TRANSMISSION_STATUS @@PACK_RECEIVED GETDATE @@PACK_SENT GETUTCDATE @@PACKET_ERRORS @@CONNECTIONS @@TIMETICKS @@CPU_BUSY @@TOTAL_ERRORS @@DBTS @@TOTAL_READ @@IDLE @@TOTAL_WRITE and @@IO_BUSY You still cannot use NEWID RAND NEWSEQUENTIALID and TEXTPTR I got that detail from SQL Server Magazine, and may have changed since publication, but the end result is - it is not a bug, you can use GETDATE() in functions, Here is more directly from the article "SQL Server 2005 Books Online (BOL) doesn't provide a reason for this change or the distinction between the functions that are and aren't allowed, but you'll notice that the functions you can't use have side effects. That is, the SQL Server 2005 non-deterministic functions that aren't allowed make internal changes in the database or the system and leave a mark (such as a change to an interval value) that they have been invoked. And UDFs aren't allowed to have side effects. For example, when SQL Server invokes the RAND function it changes an internal value that's used to calculate the seed for the next invocation of the function. This means that had SQL Server allowed you to invoke RAND within a UDF, the invocation of the UDF would have changed the result of subsequent invocations of RAND outside the UDF as well. For this reason, you can't use RAND in a UDF, even in SQL Server 2005." SQL Server 2005 has allowed some of the non-deterministic functions that were not allowed in 2000. In 2005 you can now use
CURRENT_TIMESTAMP
@@MAX_CONNECTIONS
GET_TRANSMISSION_STATUS
@@PACK_RECEIVED
GETDATE
@@PACK_SENT
GETUTCDATE
@@PACKET_ERRORS
@@CONNECTIONS
@@TIMETICKS
@@CPU_BUSY
@@TOTAL_ERRORS
@@DBTS
@@TOTAL_READ
@@IDLE
@@TOTAL_WRITE and
@@IO_BUSY

You still cannot use
NEWID
RAND
NEWSEQUENTIALID and
TEXTPTR

I got that detail from SQL Server Magazine, and may have changed since publication, but the end result is – it is not a bug, you can use GETDATE() in functions,

Here is more directly from the article

“SQL Server 2005 Books Online (BOL) doesn’t provide a reason for this change or the distinction between the functions that are and aren’t allowed, but you’ll notice that the functions you can’t use have side effects. That is, the SQL Server 2005 non-deterministic functions that aren’t allowed make internal changes in the database or the system and leave a mark (such as a change to an interval value) that they have been invoked. And UDFs aren’t allowed to have side effects. For example, when SQL Server invokes the RAND function it changes an internal value that’s used to calculate the seed for the next invocation of the function. This means that had SQL Server allowed you to invoke RAND within a UDF, the invocation of the UDF would have changed the result of subsequent invocations of RAND outside the UDF as well. For this reason, you can’t use RAND in a UDF, even in SQL Server 2005.”

]]>