<?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</title>
	<atom:link href="http://thinknook.com/category/sql-server/ssis/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>Diagnosing Kerberos Delegation Issues on SQL Server, SharePoint, SSRS and SSAS</title>
		<link>http://thinknook.com/diagnosing-kerberos-issues-with-sql-server-sharepoint-ssrs-ssas-2013-06-01/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=diagnosing-kerberos-issues-with-sql-server-sharepoint-ssrs-ssas</link>
		<comments>http://thinknook.com/diagnosing-kerberos-issues-with-sql-server-sharepoint-ssrs-ssas-2013-06-01/#comments</comments>
		<pubDate>Sat, 01 Jun 2013 13:03:42 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[MS SQL Server]]></category>
		<category><![CDATA[SSAS]]></category>
		<category><![CDATA[SSIS]]></category>
		<category><![CDATA[SSRS]]></category>
		<category><![CDATA[double-hop]]></category>
		<category><![CDATA[kerberos]]></category>
		<category><![CDATA[kerberos authentication]]></category>
		<category><![CDATA[kerberos delegation]]></category>
		<category><![CDATA[sharepoint]]></category>
		<category><![CDATA[sql server]]></category>
		<category><![CDATA[ssas]]></category>
		<category><![CDATA[ssrs]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=1106</guid>
		<description><![CDATA[Until now, I have found working with Kerberos when setting up a SQL Server stack to be a complete nightmarish experience, mainly due to two reasons: Working with Kerberos usually requires access rights to Active Directory for the account setting up this authentication protocol on the stack, in order to be able to effectively diagnose [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/diagnosing-kerberos-issues-with-sql-server-sharepoint-ssrs-ssas-2013-06-01/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SSIS vs Hadoop &#8211; a Mapping Performance Showdown</title>
		<link>http://thinknook.com/ssis-vs-hadoop-a-mapping-performance-showdown-2013-02-28/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ssis-vs-hadoop-a-mapping-performance-showdown</link>
		<comments>http://thinknook.com/ssis-vs-hadoop-a-mapping-performance-showdown-2013-02-28/#comments</comments>
		<pubDate>Thu, 28 Feb 2013 10:57:57 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[Hadoop]]></category>
		<category><![CDATA[SSIS]]></category>
		<category><![CDATA[etl]]></category>
		<category><![CDATA[hadoop]]></category>
		<category><![CDATA[map]]></category>
		<category><![CDATA[parallel processing]]></category>
		<category><![CDATA[reduce]]></category>
		<category><![CDATA[sql 2012]]></category>
		<category><![CDATA[sql server]]></category>
		<category><![CDATA[ssis]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=1015</guid>
		<description><![CDATA[On one corner we have Hadoop, a massively distributed JVM-based data processing engine with a Map &#38; Reduce API and a proven track record in handling huge data-sets. On the other corner we have SSIS, a natively non-distributed ETL engine part of the SQL Server family tool-set with .NET code extensibility features and a drag and drop [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/ssis-vs-hadoop-a-mapping-performance-showdown-2013-02-28/feed/</wfw:commentRss>
		<slash:comments>3</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>SSIS The property &#8216;ParameterName&#8217; contains invalid characters as an object name</title>
		<link>http://thinknook.com/ssis-the-property-parametername-contains-invalid-characters-as-an-object-name-2012-08-20/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ssis-the-property-parametername-contains-invalid-characters-as-an-object-name</link>
		<comments>http://thinknook.com/ssis-the-property-parametername-contains-invalid-characters-as-an-object-name-2012-08-20/#comments</comments>
		<pubDate>Mon, 20 Aug 2012 20:39:01 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SSIS]]></category>
		<category><![CDATA[job agent]]></category>
		<category><![CDATA[sql server]]></category>
		<category><![CDATA[ssis]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=685</guid>
		<description><![CDATA[Recently I&#8217;ve been getting the following error message while trying to create an SSIS 2012 step in SQL Server Job Agent, and setting the Parameters or Connection Strings for that step: The property &#8216;ParameterName&#8217; contains invalid characters as an object name. Remove the invalid characters. (Microsoft.SqlServer.Management.IntegrationServices) This error emerges after confirming the newly created step [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/ssis-the-property-parametername-contains-invalid-characters-as-an-object-name-2012-08-20/feed/</wfw:commentRss>
		<slash:comments>3</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>
		<item>
		<title>SSIS 2012 Deployment Error &#8220;The project or operation records do not exist&#8221;</title>
		<link>http://thinknook.com/ssis-2012-deployment-error-the-project-or-operation-records-do-not-exist-2012-08-03/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ssis-2012-deployment-error-the-project-or-operation-records-do-not-exist</link>
		<comments>http://thinknook.com/ssis-2012-deployment-error-the-project-or-operation-records-do-not-exist-2012-08-03/#comments</comments>
		<pubDate>Fri, 03 Aug 2012 15:00:51 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SSIS]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=660</guid>
		<description><![CDATA[Although the new SSIS 2012 Project Deployment Model is pretty cool, it is a completely new deployment architecture that is bound exhibit some bugs. To be honest SSIS 2012 in general seems to be less geared up towards enterprise level scale-out, and will work better in a non-24/7 load environment. The error I am experiencing [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/ssis-2012-deployment-error-the-project-or-operation-records-do-not-exist-2012-08-03/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SSIS 2012 &#8220;Cancelled&#8221; Status Issues</title>
		<link>http://thinknook.com/ssis-2012-cancelled-status-issues-2012-07-29/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ssis-2012-cancelled-status-issues</link>
		<comments>http://thinknook.com/ssis-2012-cancelled-status-issues-2012-07-29/#comments</comments>
		<pubDate>Sun, 29 Jul 2012 13:25:12 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SSIS]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=652</guid>
		<description><![CDATA[If you have used Microsoft development products long enough, then you must be familiar with the error reporting nightmares some of their products exhibit, the classic &#8220;please check the error log for more details&#8221; message, even though you are in the error log, is not just frustrating, but in my opinion is a bug that [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/ssis-2012-cancelled-status-issues-2012-07-29/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>SSIS Dimension Processing Error: XML parsing failed at line X, column Y: Illegal xml character.</title>
		<link>http://thinknook.com/ssis-dimension-processing-error-xml-parsing-failed-at-line-x-column-y-illegal-xml-character-2012-06-01/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ssis-dimension-processing-error-xml-parsing-failed-at-line-x-column-y-illegal-xml-character</link>
		<comments>http://thinknook.com/ssis-dimension-processing-error-xml-parsing-failed-at-line-x-column-y-illegal-xml-character-2012-06-01/#comments</comments>
		<pubDate>Fri, 01 Jun 2012 13:39:15 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SSAS]]></category>
		<category><![CDATA[SSIS]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=607</guid>
		<description><![CDATA[Without a doubt one of the most annoying and least useful errors I have ever encountered during my experience with SSIS. This error has crept up on an SSIS packages that processes a dimension. The SSIS package is very simple and all it has is a OLE DB Source that dumps data from a query [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/ssis-dimension-processing-error-xml-parsing-failed-at-line-x-column-y-illegal-xml-character-2012-06-01/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SSIS 2012 Script Component Streaming Error (0xC0047020)</title>
		<link>http://thinknook.com/ssis-2012-script-component-streaming-error-0xc0047020-2012-05-28/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ssis-2012-script-component-streaming-error-0xc0047020</link>
		<comments>http://thinknook.com/ssis-2012-script-component-streaming-error-0xc0047020-2012-05-28/#comments</comments>
		<pubDate>Mon, 28 May 2012 14:31:58 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SSIS]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=594</guid>
		<description><![CDATA[It has been a while since I released a post, this has mostly been due to a recent involvement in some very time consuming scale-out architecture, there is nothing like building a whole SQL Server architecture from scratch, something very powerful and enterprise-y. Anyhow the purpose of this post is to discuss one of the [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/ssis-2012-script-component-streaming-error-0xc0047020-2012-05-28/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.w3-edge.com/products/


Served from: thinknook.com @ 2026-05-31 01:00:11 by W3 Total Cache
-->