<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Thinknook &#187; ssis 2012</title>
	<atom:link href="http://thinknook.com/tag/ssis-2012/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinknook.com</link>
	<description>Because the world needs another Business Intelligence blog!</description>
	<lastBuildDate>Tue, 03 Jun 2014 22:09:23 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.41</generator>
	<item>
		<title>8 Ways to Optimize and Improve Performance of your SSIS Package</title>
		<link>http://thinknook.com/8-ways-to-optimize-your-ssis-package-2013-06-28/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=8-ways-to-optimize-your-ssis-package</link>
		<comments>http://thinknook.com/8-ways-to-optimize-your-ssis-package-2013-06-28/#comments</comments>
		<pubDate>Fri, 28 Jun 2013 17:30:22 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SSIS]]></category>
		<category><![CDATA[integration services]]></category>
		<category><![CDATA[ssis]]></category>
		<category><![CDATA[ssis 2012]]></category>
		<category><![CDATA[ssis parallelism]]></category>
		<category><![CDATA[ssis partitioning]]></category>
		<category><![CDATA[ssis performance]]></category>
		<category><![CDATA[ssis threading]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=1149</guid>
		<description><![CDATA[The title should actually read &#8220;8 Random Ways to Optimise SSIS&#8221;. One of the recent project I have been working on involved building a distributed (scaled-out) SSIS environment, this means multiple VMs with a standalone SSIS (2012 in Package mode) instances installed (so no SQL Server Database Engine), all pushing massive amount of data to [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/8-ways-to-optimize-your-ssis-package-2013-06-28/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Truncate SSIS Catalog Database Operation Log Tables</title>
		<link>http://thinknook.com/truncate-ssis-catalog-database-operation-log-tables-2012-11-03/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=truncate-ssis-catalog-database-operation-log-tables</link>
		<comments>http://thinknook.com/truncate-ssis-catalog-database-operation-log-tables-2012-11-03/#comments</comments>
		<pubDate>Sat, 03 Nov 2012 20:36:57 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SSIS]]></category>
		<category><![CDATA[sql server]]></category>
		<category><![CDATA[ssis]]></category>
		<category><![CDATA[ssis 2012]]></category>
		<category><![CDATA[ssis catalog]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=789</guid>
		<description><![CDATA[The SSIS Catalog in SQL Server 2012 comes with the benefit of logging natively integrated within the service&#8217;s architecture, which is awesome considering before SSIS 2012 BI developers and admins had to go for 3rd party tools in order to bring that level of logging into their SSIS packages. That being said, with a lot [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/truncate-ssis-catalog-database-operation-log-tables-2012-11-03/feed/</wfw:commentRss>
		<slash:comments>23</slash:comments>
		</item>
		<item>
		<title>Execute SSIS via Stored Procedure (SSIS 2012)</title>
		<link>http://thinknook.com/execute-ssis-via-stored-procedure-ssis-2012-2012-08-13/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=execute-ssis-via-stored-procedure-ssis-2012</link>
		<comments>http://thinknook.com/execute-ssis-via-stored-procedure-ssis-2012-2012-08-13/#comments</comments>
		<pubDate>Mon, 13 Aug 2012 18:22:01 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SSIS]]></category>
		<category><![CDATA[integration services]]></category>
		<category><![CDATA[sql 2012]]></category>
		<category><![CDATA[ssis]]></category>
		<category><![CDATA[ssis 2012]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=667</guid>
		<description><![CDATA[The SSIS 2012 Catalog integration with SQL Server comes with the advantage of being able to execute SSIS packages indigenously from within T-SQL, along with a host of other functionality including improved monitoring and logging, integrated security and obviously the new deployment model. Executing SSIS packages by calling a stored procedure can be handy in [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/execute-ssis-via-stored-procedure-ssis-2012-2012-08-13/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.w3-edge.com/products/


Served from: thinknook.com @ 2026-07-07 13:26:10 by W3 Total Cache
-->