﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Article Discussions / Article Discussions by Author / Discuss content posted by Bernabe Diaz  / Another way to get a table list from a string  / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Tue, 21 May 2013 13:59:29 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Another way to get a table list from a string</title><link>http://www.sqlservercentral.com/Forums/Topic937261-1509-1.aspx</link><description>Is the script correct? When I run it, I got an "Unclosed quotation mark after the character string '" error message. So I commented out the last + ' (that before the EXEC(@STR) statement) and could create the stored procedure.After the fix, the stored procedure seems to work fine.Best regards</description><pubDate>Mon, 09 Aug 2010 09:14:26 GMT</pubDate><dc:creator>gabriele.acconcia</dc:creator></item><item><title>RE: Another way to get a table list from a string</title><link>http://www.sqlservercentral.com/Forums/Topic937261-1509-1.aspx</link><description>This is clever and a little more flexible than some of the other techniques - and useful if all you need to do is return the output directly to the caller.  But the weakness is that the dynamic SQL means it can't be moved to a function - using a procedure really limits what you can do with the output.  I've had very good results that use a table-valued function and a numbers table to parse lists, and then the TVF results can be used in JOINs and other structs, unlike the output of a stored procedure (which can only be dumped to a temp table if further processing or filtering is required).</description><pubDate>Thu, 17 Jun 2010 11:13:12 GMT</pubDate><dc:creator>aaron.bertrand</dc:creator></item><item><title>RE: Another way to get a table list from a string</title><link>http://www.sqlservercentral.com/Forums/Topic937261-1509-1.aspx</link><description>Good parsing technique. Even though @strDataSet is declared as max, aren't the procedure parameters limited to max length of only 128 characters? That limits the longest string that can be parsed to that limit. Right?</description><pubDate>Wed, 16 Jun 2010 11:36:39 GMT</pubDate><dc:creator>sjsubscribe</dc:creator></item><item><title>RE: Another way to get a table list from a string</title><link>http://www.sqlservercentral.com/Forums/Topic937261-1509-1.aspx</link><description>Thanks for the Article.For further reading, anyone interested in using xml to split strings may be interested in this excellent blog post from Brad Schulz[url]http://bradsruminations.blogspot.com/2010/01/delimited-string-tennis-again-final.html[/url]in which he describes a few tweaks that really speed things up...</description><pubDate>Tue, 15 Jun 2010 12:35:56 GMT</pubDate><dc:creator>mister.magoo</dc:creator></item><item><title>RE: Another way to get a table list from a string</title><link>http://www.sqlservercentral.com/Forums/Topic937261-1509-1.aspx</link><description>Excellent!  I have two other procs that do this but not with such elegance.  i will be testing performance of the three versions soon and will add findings.  The other versions also return only strings.I did have to add one more single quote at the end to make it work.</description><pubDate>Tue, 15 Jun 2010 07:52:15 GMT</pubDate><dc:creator>deanroush</dc:creator></item><item><title>Another way to get a table list from a string </title><link>http://www.sqlservercentral.com/Forums/Topic937261-1509-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/scripts/T-SQL/70276/"&gt;Another way to get a table list from a string &lt;/A&gt;[/B]</description><pubDate>Tue, 15 Jun 2010 00:09:45 GMT</pubDate><dc:creator>diaz.bernabe</dc:creator></item></channel></rss>