|
Comments
|
|
I couldn't get script. Would be possible to get your scripts. My email address is bshimonov@loews.com
Thank you.
|
|
|
By the looks of the SP, I take it that you're not familiar with the tally/numbers table technique. In case my assumption is correct, I would suggest that you have a look at the following page. I was very much impressed with this technique and its applications that are mentioned in the article.
http://www.sqlservercentral.com/articles/T-SQL/62867/
Best regards,
Henk
|
|
|
I don't see why use a xml document to store the delimited values for non-2008 sql severs. I would just build a temp table in the stored proc and select from for it to return the values in a similar fashion as in SQL Server 2008 example. You will get the same results no matter which version of sql server you are running using a temp table.
|
|
|
Good information. Had to do that a few times in the past and developed my own parce string functions without the xml option however.
|
|
|
I also could not get the scripts. Could you also email this to rupeshdas@hotmail.com. The articale looks interesting.
|
|
|
great video, thanks
|
|
|
Awesome video Andy. Keep it up.
|
|
|
I am confused by your statement that table as a return type is only available in 2008. I have been using table value functions in SQL 2000. Perhaps I misunderstood.
Also, for this sort of parsing, I was expecting a tally table and I would like to know why this was not the solution chosen. I can think of many reasons, but would like to hear more about your reasons.
Love the site and the videos!
|
|
|
Gosh... I can't rate this. The XML part and the whole concept is outstanding. I just can't condone the use of a mTVF (multi-line Table Valued Function) with RBAR in it instead of using a very high speed iTVF (inline Table Valued Function) and some form of a Tally/Numbers table to replace the While Loop. Feel free to contact me if you have any questions about this comment.
--Jeff Moden
jbmoden@ameritech.net
|
|
|
excellent demo
|
|
|
Scripts link is broken. Could you please send the scripts to bob.grinde@wonderwaremidwest.com as well. Thanks
|
|
|
SQL Server 2000 has RETURNS @t TABLE in a function call.
|
|
|
Liked the technique comparison between versions
|
|
|
sweet. wish I had the code available for me to try.
|
|
|
d
|
|
|
please email code to slanka11@gmail.com
|
|
|
Very good. clear instructions and easy to follow.
|
|
|
Fixed the script link, sorry!
|
|
|
Dennis/Jeff, I know the tally number approach and it's valid, in this case I went with something different, mainly to focus on the mechanics of using functions for interesting things.
|
|
|
Andy, you rock!
|
|
|
Great stuff. Probably too much for one video but valuable and useful.
|
|
|
Very eleoquent English speaker..(use this guy for ALL your videos) ...One thing I lke to do is to enhance the functionality of functions via boolean switches..e.g. DoNotTrim, IgnoreNullOrEmptyValues etc
|
|
|
Excellent Video. Thank you
|
|
|
Great stuff Andy....thanks for the commented ack.
|
|
|
Another option to aviod the XML approach in 2005 would be using a table valued function
|
|
|
Excellent presentation.....
|
|
|
Gud one.....
|
|
|
just excellent...!! keep on doing this..!!
|
|
|
In the examples --leading delimiter with no value, does produces one row of null for the first coma, but what happened to the last coma it does not produce a row?
In --no trailing delimter, it does not have a trailing delimiter. I needed this functionality before to parse a multi-valued column but the solution was more complex that this. This is better.
|
|
|
nicely done
|
|
|
Clean and direct. Followed by the use case. Very effective. Thank you for sharing.
|
|
|
excellent splitter function
|
|
|
Little fast paced. Would be nice if he provided the code for his function as a sample.
|