|
Comments
|
|
Mention problems with BCP
|
|
|
It would have been nice if you have also discussed the IsPersisted property associated with computed columns...
|
|
|
Good.
|
|
|
good work, I wasnt know sql server provides calculated columns
|
|
Lloyd Edwards on
10/11/2009
none
|
|
|
Very good
|
|
Rob Wingate on
10/21/2009
Andy is great.
|
|
|
falling in love with this site !!! 2 thumbs up !
|
|
John Langston on
3/17/2010
Good tip
|
|
|
RAzoavel
|
|
|
Good video
|
|
|
Very quiet and hard to hear.
|
|
|
Excellent video
|
|
|
nice job
|
|
Peter Voutov on
12/6/2010
You may have mentioned "Is Persisted" property as way to "realize" columns. This may be useful in large tables involving complex calculations of computed columns that you may not want to perform on the fly.
Strangely enough, creating an index doesn't toggle the "Is Persisted" flag, which I expected it do... At least the documentation seems to require it.
http://msdn.microsoft.com/en-us/library/ms189292.aspx#BKMK_persisted
|
|
|
thanks.
|
|
|
Good One
|
|
|
I think it would have been useful to show how the second computed column index might be expanded with an included column for the email address. That would keep the resultant search from being so narrow and unrealistic as well as showing the additional flexibility one could gaine with computed columns optimally indexed.
|
|
|
Andy, if you make the calculation persistent(using the Is Persisted property) can/do you eliminate the some or all of the overhead related to searching on the column?
|
|
Richard Scott on
2/23/2012
This presenter is very easy to understand amongst those I have watched and is very concise as to the code and business reason where his presentations could apply.
|
|
|
nice
|
|
|
Very good, liked that you went into details on performance problems, gave an example of why you would use it, etc...
|
|
|
Didn't mention the added cost during inserts and updates.
|
|
|
Excellent across the board! Thank you very much!
|
|
|
I guess good to know, but goes against everything I’ve ever been taught. If I have two columns, why would I create a column in the table to concatenate them when I could do it in the query, report, etc. Just seems like a waste of space to me.
|
|
|
Seemed like a tad bit too much to cover in this mini segment, but well done nonetheless. I liked how the performance was explained.
|