﻿<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Stacia's Business Intelligence Blog: Recent Comments</title><link>http://blog.datainspirations.com</link><description /><generator>Quick Blog</generator><lastBuildDate>Sun, 07 Sep 2008 23:55:49 GMT</lastBuildDate><item><title>Comment on Configuring Reporting Services Security Correctly</title><link>http://blog.datainspirations.com/2007/11/13/configuring-reporting-services-security-correctly.aspx#comment-1146777</link><dc:creator>Enders</dc:creator><description>Great document. However you miss one step. In step 5 you change the identity of the application pool to domain\user account. You must insert a step that that domain\user account is member of the local IIS_WPG. Too bad you stopped blogging</description><guid isPermaLink="true">http://blog.datainspirations.com/2007/11/13/configuring-reporting-services-security-correctly.aspx#comment-1146777</guid><pubDate>Wed, 02 Jul 2008 09:58:53 GMT</pubDate></item><item><title>Comment on Configuring Reporting Services Security Correctly</title><link>http://blog.datainspirations.com/2007/11/13/configuring-reporting-services-security-correctly.aspx#comment-1058826</link><dc:creator>Kaisa</dc:creator><description>Brilliant document! I've also had to deal with Kerberos issues over the past 2 years, and it's quite tricky to get it right. Your document is really helpfull, especially for finding the right words to tell the customer (or their hosting provider) what to do where.</description><guid isPermaLink="true">http://blog.datainspirations.com/2007/11/13/configuring-reporting-services-security-correctly.aspx#comment-1058826</guid><pubDate>Tue, 20 May 2008 06:23:55 GMT</pubDate></item><item><title>Comment on Using a Single Package Configurations Table to Manage Package Execution on Multiple Servers</title><link>http://blog.datainspirations.com/2006/08/28/using-a-single-package-configurations-table-to-manage-package-execution-on-multiple-servers-2.aspx#comment-570623</link><dc:creator>Stacia</dc:creator><description>Hi Matthijs - There are multiple ways to work with configurations. Environment variables are simply one way. Using a dtsconfig file is another way. Can you elaborate on how you are executing your SSIS package? For example, are you running from a command line or are you using a SQL Server Agent job?</description><guid isPermaLink="true">http://blog.datainspirations.com/2006/08/28/using-a-single-package-configurations-table-to-manage-package-execution-on-multiple-servers-2.aspx#comment-570623</guid><pubDate>Mon, 01 Oct 2007 09:59:56 GMT</pubDate></item><item><title>Comment on Using a Single Package Configurations Table to Manage Package Execution on Multiple Servers</title><link>http://blog.datainspirations.com/2006/08/28/using-a-single-package-configurations-table-to-manage-package-execution-on-multiple-servers-2.aspx#comment-502284</link><dc:creator>Matthijs</dc:creator><description>Hi,&lt;BR&gt; &lt;BR&gt;I think it's a nice post, but I've got a question. Is it also possible not to use environment variables, but use .\filename.dtsconfig? Cause I switched to using this instead of an environment variable and it seems to work, only the strange thing is that after a while it's not working anymore. After a while SSIS was not able to find the config file :S... Hope you have an answer voor me. Thanks, Matthijs.</description><guid isPermaLink="true">http://blog.datainspirations.com/2006/08/28/using-a-single-package-configurations-table-to-manage-package-execution-on-multiple-servers-2.aspx#comment-502284</guid><pubDate>Mon, 01 Oct 2007 09:24:57 GMT</pubDate></item></channel></rss>