<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results for 'app:weblogs' matching tags 'SQL Server', 'SSIS', and 'logging'</title><link>http://msmvps.com/search/SearchResults.aspx?q=app:weblogs&amp;tag=SQL+Server,SSIS,logging&amp;orTags=0&amp;o=DateDescending</link><description>Search results for 'app:weblogs' matching tags 'SQL Server', 'SSIS', and 'logging'</description><dc:language>en-US</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>Auditing and Logging - make use of SSIS in SQL Server</title><link>/http://sqlserver-qa.net/blogs/bc/archive/2009/04/28/3911.aspx</link><pubDate>Tue, 28 Apr 2009 05:00:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1691457</guid><dc:creator>Anonymous</dc:creator><description>For a mintue I was thinking why I should post in this section, the variability is as per the law applicable to Financial sector to make sure the financial statement that a company reports is legitimate and that there’s no room for someone to manipulate it. As you can imagine, preventing the manipulation of the financial statement has a lot of IT impact. Some interpret the law to mean that you must audit who loaded each row into a database and when it arrived. So how can SQL Server features can help...(&lt;a href="http://sqlserver-qa.net/blogs/bc/archive/2009/04/28/3911.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=3911" width="1" height="1" alt="" /&gt;</description></item><item><title>SQL Server 2005 logging providers - make best use for SSIS packages to diagnose the issues</title><link>/http://sqlserver-qa.net/blogs/tools/archive/2008/04/09/sql-server-2005-logging-providers-make-best-use-of-ssis-too.aspx</link><pubDate>Wed, 09 Apr 2008 05:00:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1579071</guid><dc:creator>Anonymous</dc:creator><description>Log or trace of activities will help you to get detailed information on what&amp;#39;s going wrong, that too very useful for ETL based processes. In this regard within SQL Server 2005 using SSIS you can enable such logging within the package&amp;#39;s runtime. This will allow you to log the output to 5 providers, such as text file, SQL Profile trace, SQL Server table, XML file or a Windows Event log. Further you can take advantage of writing the same to 2 different providers, such as building custom logging provider....(&lt;a href="http://sqlserver-qa.net/blogs/tools/archive/2008/04/09/sql-server-2005-logging-providers-make-best-use-of-ssis-too.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=3912" width="1" height="1" alt="" /&gt;</description></item></channel></rss>