<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SQL SERVER &#8211; Shrinking Truncate Log File &#8211; Log Full</title>
	<atom:link href="http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/</link>
	<description>Notes of a SQL Server MVP and Database Administrator</description>
	<lastBuildDate>Sun, 21 Mar 2010 03:48:32 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Thom W</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-63384</link>
		<dc:creator>Thom W</dc:creator>
		<pubDate>Sun, 21 Mar 2010 03:48:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-63384</guid>
		<description>Thank you for leaving this up.  Its 11:45 pm on a Saturday night and I&#039;m dialed into my server with an outrageously large log file.  This saved my bacon, or at least kept me from having to go on site.</description>
		<content:encoded><![CDATA[<p>Thank you for leaving this up.  Its 11:45 pm on a Saturday night and I&#8217;m dialed into my server with an outrageously large log file.  This saved my bacon, or at least kept me from having to go on site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vipul</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-62771</link>
		<dc:creator>Vipul</dc:creator>
		<pubDate>Thu, 11 Mar 2010 20:45:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-62771</guid>
		<description>following only works 

USE MyDB
GO
DBCC SHRINKFILE(&#039;MyDB_log&#039;, 1)
BACKUP LOG MyDB_log WITH TRUNCATE_ONLY
DBCC SHRINKFILE(&#039;MyDB_log&#039;, 1

after I do below steps

all u have to do is doing this steps and u will shrink ur database form enterprise manager and query analyzer
1. open enterprise manager.
2. right click on the database u wanna shrink it.
3. click on properties.
4. from the data properties go to options.
5. in the middle u will see recovery model make it &quot;simple&quot; then click on &quot;ok&quot; and try to shrink the database.
it works 100%

I was getting error that all log files are in use. refer link

http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/ae4db890-c15e-44de-a2af-e85c04260331

Lot of thanks to everyone &amp; Dave</description>
		<content:encoded><![CDATA[<p>following only works </p>
<p>USE MyDB<br />
GO<br />
DBCC SHRINKFILE(&#8216;MyDB_log&#8217;, 1)<br />
BACKUP LOG MyDB_log WITH TRUNCATE_ONLY<br />
DBCC SHRINKFILE(&#8216;MyDB_log&#8217;, 1</p>
<p>after I do below steps</p>
<p>all u have to do is doing this steps and u will shrink ur database form enterprise manager and query analyzer<br />
1. open enterprise manager.<br />
2. right click on the database u wanna shrink it.<br />
3. click on properties.<br />
4. from the data properties go to options.<br />
5. in the middle u will see recovery model make it &#8220;simple&#8221; then click on &#8220;ok&#8221; and try to shrink the database.<br />
it works 100%</p>
<p>I was getting error that all log files are in use. refer link</p>
<p><a href="http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/ae4db890-c15e-44de-a2af-e85c04260331" rel="nofollow">http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/ae4db890-c15e-44de-a2af-e85c04260331</a></p>
<p>Lot of thanks to everyone &amp; Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: geva</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-62375</link>
		<dc:creator>geva</dc:creator>
		<pubDate>Mon, 08 Mar 2010 09:33:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-62375</guid>
		<description>Hi
Thanks a lot
Its working
I tried with many solutions provided by various websites.
But its working!!!!!!!!!
Thanking U Again</description>
		<content:encoded><![CDATA[<p>Hi<br />
Thanks a lot<br />
Its working<br />
I tried with many solutions provided by various websites.<br />
But its working!!!!!!!!!<br />
Thanking U Again</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-62083</link>
		<dc:creator>Pinal Dave</dc:creator>
		<pubDate>Wed, 03 Mar 2010 12:39:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-62083</guid>
		<description>Hello John,

It seems you are shrinking the data file. Shrinking a data file while the database is in use may block or hang the processes. 
If data file has a lot of free space % then use SHRINKFILE with TRUNCATE_ONLY. It would instantly release the free space to OS.

Regards,
Pinal Dave</description>
		<content:encoded><![CDATA[<p>Hello John,</p>
<p>It seems you are shrinking the data file. Shrinking a data file while the database is in use may block or hang the processes.<br />
If data file has a lot of free space % then use SHRINKFILE with TRUNCATE_ONLY. It would instantly release the free space to OS.</p>
<p>Regards,<br />
Pinal Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OW</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-62042</link>
		<dc:creator>OW</dc:creator>
		<pubDate>Tue, 02 Mar 2010 21:53:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-62042</guid>
		<description>The WITH TRUNCATE_ONLY doesnt work anymore. What should I use instead?</description>
		<content:encoded><![CDATA[<p>The WITH TRUNCATE_ONLY doesnt work anymore. What should I use instead?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jayant das</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-61922</link>
		<dc:creator>jayant das</dc:creator>
		<pubDate>Sun, 28 Feb 2010 11:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-61922</guid>
		<description>Hi

Thanks pinal 

Sometimes i was unable to shrink log from database now it&#039;s  working fine


Regards

Jayant</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>Thanks pinal </p>
<p>Sometimes i was unable to shrink log from database now it&#8217;s  working fine</p>
<p>Regards</p>
<p>Jayant</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-61918</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sun, 28 Feb 2010 09:40:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-61918</guid>
		<description>Hi Pinal,

I used without SHRINKFILE without target size (if missing, it take default size.. so i missed this parameter)
        
        DBCC SHRINKFILE (file1)

It takes long time (above 5 hours) and still the query is working.. how long it need to complete its process ?
Is it provide any problem ?

What shall i do now ?

Thanks in advance</description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>I used without SHRINKFILE without target size (if missing, it take default size.. so i missed this parameter)</p>
<p>        DBCC SHRINKFILE (file1)</p>
<p>It takes long time (above 5 hours) and still the query is working.. how long it need to complete its process ?<br />
Is it provide any problem ?</p>
<p>What shall i do now ?</p>
<p>Thanks in advance</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aizell</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-61685</link>
		<dc:creator>aizell</dc:creator>
		<pubDate>Wed, 24 Feb 2010 08:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-61685</guid>
		<description>Hi Pinal!

Thanks you very much. It really works on me.

Regards..</description>
		<content:encoded><![CDATA[<p>Hi Pinal!</p>
<p>Thanks you very much. It really works on me.</p>
<p>Regards..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-61433</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 18 Feb 2010 15:14:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-61433</guid>
		<description>Hi Pinal,

I am happy to your reply.

I will check and reply you later

Thank you ..</description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>I am happy to your reply.</p>
<p>I will check and reply you later</p>
<p>Thank you ..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-61287</link>
		<dc:creator>Pinal Dave</dc:creator>
		<pubDate>Tue, 16 Feb 2010 18:03:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-61287</guid>
		<description>Hi John,

First check the free space available in mdf file and accordingly shrink the file to set the new size. For example  a file named file1 of size 95 GB, has 15 GB free space then shrink with followinf command:
DBCC SHRINKFILE (file1, 80000)
Make sure that this process should be run in off-working hours because it could bloack user&#039;s processes.

Regards,
Pinal Dave</description>
		<content:encoded><![CDATA[<p>Hi John,</p>
<p>First check the free space available in mdf file and accordingly shrink the file to set the new size. For example  a file named file1 of size 95 GB, has 15 GB free space then shrink with followinf command:<br />
DBCC SHRINKFILE (file1, 80000)<br />
Make sure that this process should be run in off-working hours because it could bloack user&#8217;s processes.</p>
<p>Regards,<br />
Pinal Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-61227</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 16 Feb 2010 10:12:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-61227</guid>
		<description>I am working in one Data Service Process company. I was deleted 25 lakhs data from Database. After delete process, the mdf file size is increased (Before delete : 90 GB, After Delete : 95 GB). Now i am not considered about log file (ldf). 

How i decrease the size of mdf file without data loss ?

Please give me its solution

Thank you</description>
		<content:encoded><![CDATA[<p>I am working in one Data Service Process company. I was deleted 25 lakhs data from Database. After delete process, the mdf file size is increased (Before delete : 90 GB, After Delete : 95 GB). Now i am not considered about log file (ldf). </p>
<p>How i decrease the size of mdf file without data loss ?</p>
<p>Please give me its solution</p>
<p>Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ritesh Shah</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-60552</link>
		<dc:creator>Ritesh Shah</dc:creator>
		<pubDate>Tue, 02 Feb 2010 12:19:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-60552</guid>
		<description>Hi Sunil,

It is not possible to restore your database if you don&#039;t have MDF as well backup files. only log file is not enough as it doesn&#039;t have any data, it just contain transaction.</description>
		<content:encoded><![CDATA[<p>Hi Sunil,</p>
<p>It is not possible to restore your database if you don&#8217;t have MDF as well backup files. only log file is not enough as it doesn&#8217;t have any data, it just contain transaction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Udaya</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-60551</link>
		<dc:creator>Udaya</dc:creator>
		<pubDate>Tue, 02 Feb 2010 12:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-60551</guid>
		<description>Hi Pinal,

I deleted all the replication and the replication publisher as wel and recreated the publisher and replications. After doing this, when the backup job was run, the size of .bak was around 260 mb from initial 48 GB.

Regards,
Uday</description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>I deleted all the replication and the replication publisher as wel and recreated the publisher and replications. After doing this, when the backup job was run, the size of .bak was around 260 mb from initial 48 GB.</p>
<p>Regards,<br />
Uday</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sunil</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-60544</link>
		<dc:creator>Sunil</dc:creator>
		<pubDate>Tue, 02 Feb 2010 09:28:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-60544</guid>
		<description>Hello,

I have one question which i am just able to find answer for.
Suppose I have my .mdf file on D drive and .ldf file on E drive and due to some reason my D drive crash, and all my backup is also on D drive. So now if i want to restore my database in minimum possible time then how will I restore database now that i dont have my mdf file as D drive is not available.
If any one can answer this question then it will be of great help to me...

Thanks in advance.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I have one question which i am just able to find answer for.<br />
Suppose I have my .mdf file on D drive and .ldf file on E drive and due to some reason my D drive crash, and all my backup is also on D drive. So now if i want to restore my database in minimum possible time then how will I restore database now that i dont have my mdf file as D drive is not available.<br />
If any one can answer this question then it will be of great help to me&#8230;</p>
<p>Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bobbili</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-60310</link>
		<dc:creator>Bobbili</dc:creator>
		<pubDate>Thu, 28 Jan 2010 05:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-60310</guid>
		<description>--To know the ope transactions
DBCC OPENTRAN(SPID)
--To kill any SPID&#039;s

KILL  </description>
		<content:encoded><![CDATA[<p>&#8211;To know the ope transactions<br />
DBCC OPENTRAN(SPID)<br />
&#8211;To kill any SPID&#8217;s</p>
<p>KILL</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bobbili</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-60309</link>
		<dc:creator>Bobbili</dc:creator>
		<pubDate>Thu, 28 Jan 2010 05:15:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-60309</guid>
		<description>Its an handy script for the DBA&#039;s.----Bobbili Venkateswara Ra0</description>
		<content:encoded><![CDATA[<p>Its an handy script for the DBA&#8217;s.&#8212;-Bobbili Venkateswara Ra0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ab</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-59927</link>
		<dc:creator>Ab</dc:creator>
		<pubDate>Tue, 19 Jan 2010 09:07:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-59927</guid>
		<description>This works! just wanna make everyone rest assured:)</description>
		<content:encoded><![CDATA[<p>This works! just wanna make everyone rest assured:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Udaya</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-59872</link>
		<dc:creator>Udaya</dc:creator>
		<pubDate>Mon, 18 Jan 2010 04:49:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-59872</guid>
		<description>Hi Pinal,

Sorry for the late reply, I was on vacations.

I went through some of the articles on how to kill a process.
In some article they refer to SPID. How do I get the SPID for the open transaction.

Its a production server and replications are active, the replications are scheduled once in every 4 hrs.

Please let know know if there are any command or script that needs to be executed to kill the process.</description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>Sorry for the late reply, I was on vacations.</p>
<p>I went through some of the articles on how to kill a process.<br />
In some article they refer to SPID. How do I get the SPID for the open transaction.</p>
<p>Its a production server and replications are active, the replications are scheduled once in every 4 hrs.</p>
<p>Please let know know if there are any command or script that needs to be executed to kill the process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-59590</link>
		<dc:creator>Pinal Dave</dc:creator>
		<pubDate>Mon, 11 Jan 2010 17:55:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-59590</guid>
		<description>Hi Udaya,

As the OPENTRAN resturn on process, that means one transaction is running and you need to stop that.
If the data is not replicated then kill that process.

Every time sp would be called the temp table would be created and if you think creating a temp table is taking time then keep a table in database and use it in your SP.

Regards,
Pinal Dave</description>
		<content:encoded><![CDATA[<p>Hi Udaya,</p>
<p>As the OPENTRAN resturn on process, that means one transaction is running and you need to stop that.<br />
If the data is not replicated then kill that process.</p>
<p>Every time sp would be called the temp table would be created and if you think creating a temp table is taking time then keep a table in database and use it in your SP.</p>
<p>Regards,<br />
Pinal Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Udaya</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-59575</link>
		<dc:creator>Udaya</dc:creator>
		<pubDate>Mon, 11 Jan 2010 12:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-59575</guid>
		<description>Many Thanks for the reply Mr Pinal.

When the database was created the size mentioned was 2 mb and incremental was 10%.

I have executed DBCC OPENTRAN, 
Output - Replicated Transaction Information:
        Oldest distributed LSN     : (2091:12488:1)
        Oldest non-distributed LSN : (2232:124689:1)

Space Available : 16.85 mb

I did shrink the database with the above command

DBCC SHRINKFILE(, 1)
BACKUP LOG  WITH TRUNCATE_ONLY
DBCC SHRINKFILE(, 1)
GO 

but nothing seems to happen, the size is 47 GB.

--- Stored procedure ---
Sorry, missed to mention, we are using single user id login in the reporting application. If any user access the application same authentication is used.

In this the case, I belive the table would be rewritten, if the second user accesses the report.
 
Is there any work around?


When the sp is executed by users at the same time, the execution time is more. for instance when executed by a single user it takes 30 - 40 secs, where as when multiple user execute, its around a minute +.

Is this cos the sp is trying to access the same table, its slow.

Regards,
Uday</description>
		<content:encoded><![CDATA[<p>Many Thanks for the reply Mr Pinal.</p>
<p>When the database was created the size mentioned was 2 mb and incremental was 10%.</p>
<p>I have executed DBCC OPENTRAN,<br />
Output &#8211; Replicated Transaction Information:<br />
        Oldest distributed LSN     : (2091:12488:1)<br />
        Oldest non-distributed LSN : (2232:124689:1)</p>
<p>Space Available : 16.85 mb</p>
<p>I did shrink the database with the above command</p>
<p>DBCC SHRINKFILE(, 1)<br />
BACKUP LOG  WITH TRUNCATE_ONLY<br />
DBCC SHRINKFILE(, 1)<br />
GO </p>
<p>but nothing seems to happen, the size is 47 GB.</p>
<p>&#8212; Stored procedure &#8212;<br />
Sorry, missed to mention, we are using single user id login in the reporting application. If any user access the application same authentication is used.</p>
<p>In this the case, I belive the table would be rewritten, if the second user accesses the report.</p>
<p>Is there any work around?</p>
<p>When the sp is executed by users at the same time, the execution time is more. for instance when executed by a single user it takes 30 &#8211; 40 secs, where as when multiple user execute, its around a minute +.</p>
<p>Is this cos the sp is trying to access the same table, its slow.</p>
<p>Regards,<br />
Uday</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-59566</link>
		<dc:creator>Pinal Dave</dc:creator>
		<pubDate>Mon, 11 Jan 2010 09:09:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-59566</guid>
		<description>Hi Udaya,

In database property check the &quot;Space available&quot;. IF this is near about the size of transaction log then it shoud be shrunk. If this value is small then check whether any transaction is running from long using DBCC OPENTRAN.
It may be that you assigned the 47 GB space to .ldf file at the time of database creation. If that is the case then use DBCC SHRINKFILE and define the free space size.

About temp table: Don&#039;t worry sql server handle the issue you are suspecting and uses the same approach that you are thinking to plan manually.
A temp table (not global temp table) is available only to the session that created it. Multiple user can create temp table with same name at the same time because sql server internally use session id in there name to uniquify them.

Regards,
Pinal Dave</description>
		<content:encoded><![CDATA[<p>Hi Udaya,</p>
<p>In database property check the &#8220;Space available&#8221;. IF this is near about the size of transaction log then it shoud be shrunk. If this value is small then check whether any transaction is running from long using DBCC OPENTRAN.<br />
It may be that you assigned the 47 GB space to .ldf file at the time of database creation. If that is the case then use DBCC SHRINKFILE and define the free space size.</p>
<p>About temp table: Don&#8217;t worry sql server handle the issue you are suspecting and uses the same approach that you are thinking to plan manually.<br />
A temp table (not global temp table) is available only to the session that created it. Multiple user can create temp table with same name at the same time because sql server internally use session id in there name to uniquify them.</p>
<p>Regards,<br />
Pinal Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Udaya</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-59562</link>
		<dc:creator>Udaya</dc:creator>
		<pubDate>Mon, 11 Jan 2010 07:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-59562</guid>
		<description>Hi there,

I have two queries one pertaining to Sql Transaction log bulky and second regarding to stored procedures.

Sql Transaction log - I have production database with the data file size of 240 mb and log file size of 47 GB.
We have scheduled for a full backup everyday. The database is in the simple recovery mode. Intially when the database was backuped, the .bak was same as data file.
We tired backing up the transactional log, but no luck, and tried with DBCC Shrink no effect, the log file is still the same.

Kindly suggest.

Stored procedures - We have written a stored procedure for reports, which uses number of temp tables for computation.
Now my query is, if the sp is executed by multiple users at same instance or time, will the sp executes, will the output be correct and will the time taken for execution be more.

Is there any possiblity to generate dynamic temp table,
for e.g create table with the session Id.

If there are any suggestion please do suggest.
We need to implement the report with sp, any work around.</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>I have two queries one pertaining to Sql Transaction log bulky and second regarding to stored procedures.</p>
<p>Sql Transaction log &#8211; I have production database with the data file size of 240 mb and log file size of 47 GB.<br />
We have scheduled for a full backup everyday. The database is in the simple recovery mode. Intially when the database was backuped, the .bak was same as data file.<br />
We tired backing up the transactional log, but no luck, and tried with DBCC Shrink no effect, the log file is still the same.</p>
<p>Kindly suggest.</p>
<p>Stored procedures &#8211; We have written a stored procedure for reports, which uses number of temp tables for computation.<br />
Now my query is, if the sp is executed by multiple users at same instance or time, will the sp executes, will the output be correct and will the time taken for execution be more.</p>
<p>Is there any possiblity to generate dynamic temp table,<br />
for e.g create table with the session Id.</p>
<p>If there are any suggestion please do suggest.<br />
We need to implement the report with sp, any work around.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linda_web@yahoo.com</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-59163</link>
		<dc:creator>linda_web@yahoo.com</dc:creator>
		<pubDate>Thu, 31 Dec 2009 00:50:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-59163</guid>
		<description>Hello to all,

We have SQL 2000 with very big database about 500 GB.
We deleted about 50% of the data, we dropped all indexes
With simple recovery option. (allot of image BOLB fields)

However, the database size increased after delete process, we ran dbcc shrink db
And shrink file, but the size still same.

Any idea to get rid of all empty spaces, and what the best practice to reduce the size to 250 GB? 
Note: we don’t have much space to move the database around

Thanks in advance
Linda</description>
		<content:encoded><![CDATA[<p>Hello to all,</p>
<p>We have SQL 2000 with very big database about 500 GB.<br />
We deleted about 50% of the data, we dropped all indexes<br />
With simple recovery option. (allot of image BOLB fields)</p>
<p>However, the database size increased after delete process, we ran dbcc shrink db<br />
And shrink file, but the size still same.</p>
<p>Any idea to get rid of all empty spaces, and what the best practice to reduce the size to 250 GB?<br />
Note: we don’t have much space to move the database around</p>
<p>Thanks in advance<br />
Linda</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nelson</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-59152</link>
		<dc:creator>Nelson</dc:creator>
		<pubDate>Wed, 30 Dec 2009 20:08:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-59152</guid>
		<description>Hi,

I have a bunch of databases SQL Server 2005) whose logs have been growing too big recently. Two of them refuse to truncate the logs after a scheduled job runs a log backup. I have since run manual backups to disk and with truncate_only option but they will not truncate. 

Is there any reason why these will not truncate and how can I force the truncate since we are running out of SAN space?

Sincerely,
Nelson.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I have a bunch of databases SQL Server 2005) whose logs have been growing too big recently. Two of them refuse to truncate the logs after a scheduled job runs a log backup. I have since run manual backups to disk and with truncate_only option but they will not truncate. </p>
<p>Is there any reason why these will not truncate and how can I force the truncate since we are running out of SAN space?</p>
<p>Sincerely,<br />
Nelson.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Prashant dasi</title>
		<link>http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-59053</link>
		<dc:creator>Prashant dasi</dc:creator>
		<pubDate>Mon, 28 Dec 2009 10:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-59053</guid>
		<description>can anyone help or guide me 
creating the replication of the database 
for sql 2000 / 2005</description>
		<content:encoded><![CDATA[<p>can anyone help or guide me<br />
creating the replication of the database<br />
for sql 2000 / 2005</p>
]]></content:encoded>
	</item>
</channel>
</rss>
