<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Using an SSIS package to monitor and archive the default trace file</title><link>http://blogs.msdn.com/benjones/archive/2009/05/13/using-an-ssis-package-to-monitor-and-archive-the-default-trace-file.aspx</link><description>I find it frustrating that the SQL Server 2005/2008 default trace is continually overwritten and there is no way to store x number of files or x MBs of data.&amp;#160; As a workaround, I developed an SSIS package to monitor the \LOG folder and automatically</description><dc:language>en-GB</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Using an SSIS package to monitor and archive the default trace file | ASP NET Hosting</title><link>http://blogs.msdn.com/benjones/archive/2009/05/13/using-an-ssis-package-to-monitor-and-archive-the-default-trace-file.aspx#9610280</link><pubDate>Wed, 13 May 2009 21:27:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9610280</guid><dc:creator>Using an SSIS package to monitor and archive the default trace file | ASP NET Hosting</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://asp-net-hosting.simplynetdev.com/using-an-ssis-package-to-monitor-and-archive-the-default-trace-file/"&gt;http://asp-net-hosting.simplynetdev.com/using-an-ssis-package-to-monitor-and-archive-the-default-trace-file/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>