|
Comments
|
|
Hard to follow. You went too fast
|
|
Thomas Kelley on
3/23/2009
Thank you for taking the time to show this functionality.
|
|
|
Good useful information I can use on the job. Thank you!
|
|
|
10x
|
|
Bill Portman on
3/23/2009
This has huge performance implications as well as hard to manage and potentially problematic hidden code. Definately, use caution.
|
|
|
too short
|
|
|
Thanks. Is the computed column evaluated even if not selected (and other columns of table selected)?
|
|
|
NO, the function that is referenced in a computed column but not used in the query is not executed.
|
|
|
Would it probably be better to do a JOIN and use a view instead of this technique? When would it be better to use a computed column instead of JOINing?
|
|
|
Although, a computed column based on a scalar udf call may easily bring performace problems, it is a really awesome to know about this feature. This feature is completely unexpected and looks like the way to go, if for example, this scalar udf, which is returning a value, is making a select on a table of at most 100 rows or less. If the table this udf is calling doesnt change, you might want to make this udf deterministic. Just awesome!! Thank you.
|
|
|
very usefull...
Thanks ..
|
|
|
I am new to UDF's for me the author was going pretty fast in explaining stuff.
|
|
Shaun Turner on
7/13/2011
use caution? or what's the point?
There are many ways in SQL that you can hack around the Servers own constraints in order to do things that it wasn't designed to do, doesn't mean that we want to use it or need a demo showing us the wrong way of doing things?
Sorry not trying to be difficult
|
|
|
simple and clear
|
|
Dennis Allen on
7/14/2011
If the desired shape of the data was a single object that had the two output columns, would it not in all cases be better to use a view to join the needed tables to get the same results as the scalar function bound to the computed column?
|
|
|
No sound
|
|
|
I watched it with sound turned down (so as not to annoy colleagues), but still understood - very clear.
|
|
|
a slightly obtuse example
|
|
|
The content was good, but the example tables and data were overly complicated. This caused me to be focusing on the structure of the data instead of the lesson being taught.
|
|
|
The narrator went pretty fast and I didn't get a chance to review the code.
|
|
|
Thanks
|
|
|
I am so glad you gave the warning at the end!
|
|
|
The sound was difficult to hear.
|
|
|
Thanks ... I was not known that.... Thanks a lot dude..
|
|
|
Very good. More Power. - Domingo M. Asuncion
|
|
|
Good information.
|
|
Pete Williams on
8/19/2011
The most important message here is this is inefficient, so use with caution, but it works.
|
|
|
Very useful...
|
|
|
Good
|
|
|
Good material, if you've done something similar in nature..
|
|
|
Helpful.
|
|
Maurice Ivory on
1/17/2012
Interesting Video, I learned something I didn't know.
|