﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Integration Services / Data Warehousing  / ssis data flow transform question / 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>Wed, 19 Jun 2013 00:17:08 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: ssis data flow transform question</title><link>http://www.sqlservercentral.com/Forums/Topic1369163-364-1.aspx</link><description>You can also use a multicast to direct the recordset to multiple Destination objects in one Data Flow.</description><pubDate>Mon, 08 Oct 2012 07:17:45 GMT</pubDate><dc:creator>Thomas LeBlanc</dc:creator></item><item><title>RE: ssis data flow transform question</title><link>http://www.sqlservercentral.com/Forums/Topic1369163-364-1.aspx</link><description>thanks very much for the replies guysill look into both methods</description><pubDate>Mon, 08 Oct 2012 02:48:38 GMT</pubDate><dc:creator>erics44</dc:creator></item><item><title>RE: ssis data flow transform question</title><link>http://www.sqlservercentral.com/Forums/Topic1369163-364-1.aspx</link><description>You might want to look into the use of .RAW files in SSIS.  They're basically SSIS's version of temp tables.  What they do is pull off a single system into a file (local to the SSIS server is best) in a high-speed access version of the data (you won't be able to read it directly).That raw can then be manipulated repeatedly.  My personal use for it is usually when dealing with multiple warehouses, where I need to do heavy transforms and then port the results to multiple targets.  First I'll do all the transforms into the raw, and then start pumping it out to the target systems.  The reason for this is so I can checkpoint the transformation, keeping me from having to hit the source system more than once in case of a connection failure or somesuch.</description><pubDate>Fri, 05 Oct 2012 13:01:47 GMT</pubDate><dc:creator>Evil Kraig F</dc:creator></item><item><title>RE: ssis data flow transform question</title><link>http://www.sqlservercentral.com/Forums/Topic1369163-364-1.aspx</link><description>your best solution would be to create multiple dataflows in the control flow area of your package.create your first dataflow to move the data to the single table on your new server.the create the remaining data flows within a sequence container and use the control flow expressions to completetion to ensure your data flows then execute in the correct order .....alternatively, you may just want to have a second data flow reading of the single table and use conditional splits to split the data into logic paths........(I don't know your data or it's complexity but is an alternative). Hope that helps</description><pubDate>Fri, 05 Oct 2012 10:40:58 GMT</pubDate><dc:creator>dave-dj</dc:creator></item><item><title>ssis data flow transform question</title><link>http://www.sqlservercentral.com/Forums/Topic1369163-364-1.aspx</link><description>HiI have one large table in one database and i am am going to move the data and turn it into a normalised relational database with a number of tables.As all the data is coming from a single table is there a way of just importing it once (say into a recordset or something) and then running other data flow tasks from that recordset?and is there a pause transform that will wait till one item is finished before starting?Thanks in advance</description><pubDate>Fri, 05 Oct 2012 09:56:34 GMT</pubDate><dc:creator>erics44</dc:creator></item></channel></rss>