﻿<?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 Adam Aspin  / SQL vs. SSIS - SCD / 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>Sun, 26 May 2013 00:59:38 GMT</lastBuildDate><ttl>20</ttl><item><title>SQL vs. SSIS - SCD</title><link>http://www.sqlservercentral.com/Forums/Topic1128034-1497-1.aspx</link><description>Excellent article. Has anyone done any comparisons between SQL MERGE and the equivalent using SSIS (not using the standard SSIS SCD transform) ? and what were the results ?Any further tips in deciding whether to go the SQL MERGE route or SSIS route ?My take on it is as follows: SSIS is good for orchestrating workflow, and its data pipeline (eg inserting records in a table) and not  good at batch processes such as updating tables. The standard SSIS SCD transform is a pain to work iteratively with - avoid.. My heart says build a USP with SQL MERGE, and execute the USP from a SQL task in SSIS. You can edit, update &amp; tweak the USP to your heart's content and not necessarily affect the SSIS package.Obviously the above is very simplistic, what do others think ?Regards Geoff:-)</description><pubDate>Mon, 20 Jun 2011 03:02:26 GMT</pubDate><dc:creator>Geoff Johns</dc:creator></item></channel></rss>