<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblogcasts.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Jay Uttam - All Comments</title><link>http://sqlblogcasts.com/blogs/jay_uttam/default.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2007.1 (Build: 20917.1142)</generator><item><title>re: Range Lookup in SSIS</title><link>http://sqlblogcasts.com/blogs/jay_uttam/archive/2008/02/17/range-lookup-in-ssis.aspx#12934</link><pubDate>Wed, 27 Jan 2010 20:20:44 GMT</pubDate><guid isPermaLink="false">fa8c4e8e-46a3-4193-8264-2c1a9cb3475d:12934</guid><dc:creator>CozyRoc</dc:creator><description>&lt;p&gt;There is solution based on the third-party commercial CozyRoc SSIS+ library. CozyRoc has implemented data flow destination script, which creates memory-efficient range dictionary object. The dictionary object can then be used in CozyRoc Lookup Plus component. For more information and demonstration how to use the script, check here:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.cozyroc.com/script/range-dictionary-destination"&gt;www.cozyroc.com/.../range-dictionary-destination&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=12934" width="1" height="1"&gt;</description></item><item><title>re: Range Lookup in SSIS</title><link>http://sqlblogcasts.com/blogs/jay_uttam/archive/2008/02/17/range-lookup-in-ssis.aspx#7566</link><pubDate>Wed, 20 Feb 2008 12:21:21 GMT</pubDate><guid isPermaLink="false">fa8c4e8e-46a3-4193-8264-2c1a9cb3475d:7566</guid><dc:creator>simonsabin</dc:creator><description>&lt;p&gt;I've found to get the best performance you need to use a script component and load your dataset into memory (usual caveats about available memory etc) and then you can use the binary search to find the value you want. This will be far quicker than having to make a database call for every unique value that comes along. &lt;/p&gt;
&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=7566" width="1" height="1"&gt;</description></item></channel></rss>
