<?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; log</title>
	<atom:link href="http://thinknook.com/tag/log/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>Why is my SQL Server Transaction Log not Shrinking (or Reusing the Log file)?</title>
		<link>http://thinknook.com/why-is-my-sql-server-log-file-not-shrinking-or-reusing-the-log-file-2012-11-02/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=why-is-my-sql-server-log-file-not-shrinking-or-reusing-the-log-file</link>
		<comments>http://thinknook.com/why-is-my-sql-server-log-file-not-shrinking-or-reusing-the-log-file-2012-11-02/#comments</comments>
		<pubDate>Fri, 02 Nov 2012 13:15:50 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[database growth]]></category>
		<category><![CDATA[dmv]]></category>
		<category><![CDATA[log]]></category>
		<category><![CDATA[sql server]]></category>
		<category><![CDATA[transaction log]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=784</guid>
		<description><![CDATA[Trying to figure-out why your log file for a particular database is not &#8220;naturally&#8221; shrinking is the first steps you need to take in order to diagnose and resolve a large SQL Server transaction log file. Transaction Log files generally grow because there is something that is stopping SQL Server from reusing the already allocated [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/why-is-my-sql-server-log-file-not-shrinking-or-reusing-the-log-file-2012-11-02/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Troubleshooting a Large SQL Server Transaction Log File</title>
		<link>http://thinknook.com/troubleshooting-large-sql-server-transaction-log-2011-08-07/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=troubleshooting-large-sql-server-transaction-log</link>
		<comments>http://thinknook.com/troubleshooting-large-sql-server-transaction-log-2011-08-07/#comments</comments>
		<pubDate>Sun, 07 Aug 2011 13:51:45 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SQL Server DBA]]></category>
		<category><![CDATA[database growth]]></category>
		<category><![CDATA[log]]></category>
		<category><![CDATA[sql server]]></category>
		<category><![CDATA[transaction log]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=132</guid>
		<description><![CDATA[Managing space on your SQL Server Transaction Log can sometimes be daunting, usually if you have a good backup strategy, and a well moderated database (in terms of monitoring and flagging long running transactions), then you will rarely run into unexpected large growth of your transaction log file. But in the real world this is [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/troubleshooting-large-sql-server-transaction-log-2011-08-07/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.w3-edge.com/products/


Served from: thinknook.com @ 2026-04-15 00:30:36 by W3 Total Cache
-->