Comments on: SQL SERVER – Shrinking Truncate Log File – Log Full – Part 2 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/ SQL, SQL Server, MySQL, Big Data and NoSQL Wed, 19 Jun 2013 21:45:15 +0000 hourly 1 http://wordpress.com/ By: Diwakar http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-379739 Sat, 24 Nov 2012 02:56:48 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-379739 Hi

I need one help very badly. My scenario is like this. I have1 DB on an Instance which is having a data of almost 50GB with around 20 million records. And we have one job after running which the data or records in the DB1 are pushed into an another DB which is running on another Instance. But the bad thing is that the Log file(on Instance 2) is getting filled and the job getting failed. I already kept the Log Drive size as 68GB and I can’t afford more than that. So is there any chance or settings by setting which the log file will be shrinked on fly and the transaction continues.

]]> By: SQL SERVER – Weekly Series – Memory Lane – #004 « SQL Server Journey with SQL Authority http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-379680 Sat, 24 Nov 2012 01:31:18 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-379680 [...] Shrinking Truncate Log File – Log Full – Part 2 Shrinking database or mdf file is indeed bad thing and it creates lots of problems. However, once in a while there is legit requirement to shrink the log file – a very rare one. In the rare occasion shrinking or truncating the log file may be the only solution. However, one should make sure to take backup before and after the truncate or shrink as in case of a disaster they can be very useful. Remember that truncating log file will break the log chain and while restore it can create major issue. Anyway, use this feature with caution. [...]

]]> By: Armstrong Henderson http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-252558 Tue, 14 Feb 2012 20:01:05 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-252558 So easy i wish had thought of it. I’m on SQL Express 2008 r2 and it worked just fine.

]]> By: Malaya Sinha http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-227202 Wed, 28 Dec 2011 05:03:08 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-227202 Hi,
If the log file size is huge and you are not able to truncate it then you can try these steps as well.
1. Goto to database properties.
2. Goto options.
3. Change the recovery model to simple and click over ok.
4. Restart the database.
5. Try shrinking the log file.

]]> By: Anton http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-202272 Tue, 22 Nov 2011 15:37:00 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-202272 Hi Pinal,
thank you for this post. I initially had the same problem as Yasemin but found if the reference to the log file is removed when re-attaching, your solution works perfectly.

]]> By: jernas solomon http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-80903 Tue, 20 Jul 2010 09:43:13 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-80903 Hi pinal

how to create email alert for log is full in database.

please help me….

]]> By: Yasemin http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-56880 Thu, 22 Oct 2009 00:40:07 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-56880 Hi!
What about removing the log file in Ms Sql 2008?
I tried to Detach&Attach the database, however I can’t attach it without the log file..
thank you,
yasemin

]]> By: Udaya http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-55595 Fri, 04 Sep 2009 11:58:53 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-55595 Hi Pinal,

Even after executing the above shrink query the size of the log file has not reduced. In my case the data file is around 180 mb, where as Log file is aroung 32 GB. Please let me know the log maintenance procedure to reduce the log file size.

Regards,
Uday

]]> By: Uma http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-55436 Mon, 31 Aug 2009 16:06:35 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-55436 Hi Pinal, I am using SQL Server 2005 Management studio and connected to SQL Server 2000 instance and I am able to get rid of the promary log file completely.
Thanks for posting the solution.

]]> By: Devang http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-51753 Mon, 11 May 2009 03:07:25 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-51753 this will not be done if database is mirrored., Whats procedure to shiriking mirror database.

]]> By: Dale http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-49192 Mon, 16 Mar 2009 13:23:19 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-49192 I just tried II. Eliminate the log file completely. The trick worked PERFECTLY!

Thank you for posting the solution!

]]> By: ajay http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-44821 Mon, 15 Dec 2008 16:30:20 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-44821 I am presently working on Upgradation project and the SQL Server is development phase n we are getting data from another database through SSIS. I am experiencing performance problem, where there are only 20-30 users who are using the SQL. There is a very slow running SSIS packages and sometimes they are stopping due to unkown reason n if they leave them..the next day its show tht the SSIS package ran successful. what are the things I am suppose to check for?..plz suggest me how to check the loading performance as its bulk loads n even mass updates are ran on the loaded tables.

thanks and regards

]]> By: ScottG http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-44203 Thu, 13 Nov 2008 15:22:51 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-44203 Very nice and helpful article. Got a log file down from 524 meg to 500 k.

]]> By: Senthil kumar Rajendran http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-42664 Wed, 10 Sep 2008 21:59:06 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-42664 We have an option with one of our server like disk space alert, when the usage os disk reaches 90-95% it wil create an alert and send an email to all DBA.

All the time Critical suituation is due to growth of LOG files only, rarely on MDF files. Is there any query to find which file MDF/LDF is growing or which is adapting more space.

Is there any way to find the file in short time period because we have to resolve it as quick as posible.

Regards,

Senthil kumar Rajendran.

]]> By: Darshan shah http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-39899 Tue, 08 Jul 2008 09:53:50 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-39899 Hi Pinal ,

If i create second log file for the one database. so how it works ?

]]> By: Mark Kamoski http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-37829 Mon, 12 May 2008 18:30:06 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-37829 Can one programmatically schedule this?

If yes, then what would the BAT file look like?

Please advise.

Thank you.

– Mark Kamoski

]]> By: Gaurav http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-33386 Thu, 31 Jan 2008 11:12:27 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-33386 Hi Sukh,
You need to find the Log file folder in your Windows folders by going to place where your SQL server is installed and has its data files. The path should be something like.. ‘D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\’. There you will see your Log file and MDF file.

- Gaurav

]]> By: Sukh http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-33200 Tue, 22 Jan 2008 22:27:03 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-33200 Sorry, i attached the detached file by right clicking on database->attach. But my questions of finding log folder is still unsolved.

]]> By: Sukh http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-33199 Tue, 22 Jan 2008 22:23:00 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-33199 Hi,

i am using sql server 2005 express edition,
I detach the database but i couldn’t find log folder anywhere. There is SQL serve logs folder under Management folder but it is not showing any rename option after right clicking on it, it just shows Refresh.
How can bring back my detach database as i don’t have any backup for that.

]]> By: SQL SERVER - Solution - Log File Very Large - Log Full Journey to SQL Authority with Pinal Dave http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-26572 Mon, 17 Dec 2007 13:45:25 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-26572 [...] SQL SERVER – Shrinking Truncate Log File – Log Full – Part 2(Management Studio) [...]

]]> By: Shannon Justice http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-25819 Thu, 13 Dec 2007 21:44:42 +0000 http://blog.sqlauthority.com/2007/11/22/sql-server-shrinking-truncate-log-file-log-full-part-2/#comment-25819 I have noticed that you have not included a step of backing up the database first, and when doing so, clicking remove inactive entries will verify that all transactions have made it through the log before deleting it. I have avoided the dreaded “Unable to Attach” corruption error by doing this fashion. Thanks for having a great site, although I am disappointed in your decision to not write 2k tips anymore. I understand it, but still have clients from all over who are still running 2k and will for quite a while longer. Still, thanks for all you do!

Shannon

]]>