|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Monday, September 10, 2012 10:30 AM
Points: 480,
Visits: 461
|
|
| The problem I've seen is that once you start doing these kinds of "dirty tricks" that the dirty tricks eventually become seen as acceptable when really they never should be. Better to run a "tight ship" and be secure.
|
|
|
|
|
SSCrazy Eights
        
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 11:17 AM
Points: 9,855,
Visits: 9,376
|
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 2:57 AM
Points: 38,071,
Visits: 30,365
|
|
RBarryYoung (1/13/2009) And the SQL parser, optimizer and data engine rely heavily on the assumption that functions cannot cause changes in the database while they are being invoked. Almost all of the restrictions in UDF revolve around insuring that this is the case.
And one of the reasons for that is so that the optimiser is free to pick execution plans without worrying about how many times the function will be executed.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|