﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on That might take a while...</title><description>I didn't have a clue that the table was this big. I will probably need to rethink the way we do it.
  
  
Thanks for the tip
</description><link>http://ayende.com/2303/that-might-take-a-while#comment2</link><guid>http://ayende.com/2303/that-might-take-a-while#comment2</guid><pubDate>Wed, 11 Apr 2007 05:32:11 GMT</pubDate></item><item><title>SSIS Guy commented on That might take a while...</title><description>On large tables, it's usually more efficient to put the data flow in a for loop and chunk through it in blocks of (50k, 100k, etc.) rows. If you've got a sequential PK, then this is pretty easy.
  
  
It's much easier for the query processor to deal with smaller chunks of data at one time, and SSIS likes it better too.
  
</description><link>http://ayende.com/2303/that-might-take-a-while#comment1</link><guid>http://ayende.com/2303/that-might-take-a-while#comment1</guid><pubDate>Wed, 11 Apr 2007 05:11:23 GMT</pubDate></item></channel></rss>