<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
SQL Server 2005 Performance Tuning
»
Clearing LOD file (126 GB)
15 posts, Page 1 of 2
1
2
»»
Clearing LOD file (126 GB)
Rate Topic
Display Mode
Topic Options
Author
Message
Joy Smith San
Joy Smith San
Posted Thursday, August 21, 2008 2:31 AM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 3:25 AM
Points: 1,371,
Visits: 2,302
Dear All,
One of our client's server is in Germany. We have made a project for them recently. It got crashed today.When I checked I found that MDF size is hardly 256MB and LDF is 126GB (huuuge)...
How can I clear the LOG..? Wot are the things need to be done before clearing LOG...? Please guide me..Very urgent..
Thanks in advance...
Dear freind Marsh -- I expect an ealry reply from you especialy...
Santhos Nahir (India)
Post #556344
Hadrian
Hadrian
Posted Thursday, August 21, 2008 2:47 AM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 1:28 PM
Points: 1,156,
Visits: 2,195
hello
first dbcc loginfo and check status column may be 0 or 2 ,if 0 you can
backup log dn_name with truncate _only
go
dbcc shrinkfile(log_file_id or file_name,size you want to shrink)
go
Post #556351
Andras Belokosztolszki
Andras Belokosztolszki
Posted Thursday, August 21, 2008 2:54 AM
Ten Centuries
Group: General Forum Members
Last Login: Thursday, January 26, 2012 5:26 AM
Points: 1,367,
Visits: 1,585
And after you follow Hadrian's advice, take a full backup. Then find out if that database had any periodic full/log backups. If yes, try to find the reason for the large transaction log. If no, then set up periodic database and log backups (or if the recovery requirements permit it set it to simple recovery mode)
Regards,
Andras
Andras Belokosztolszki, MCPD, PhD
GoldenGate Software
Post #556355
Joy Smith San
Joy Smith San
Posted Thursday, August 21, 2008 3:04 AM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 3:25 AM
Points: 1,371,
Visits: 2,302
Thanks a lot. will try the same...
Post #556358
Joy Smith San
Joy Smith San
Posted Thursday, August 21, 2008 3:08 AM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 3:25 AM
Points: 1,371,
Visits: 2,302
Hello,
The problem is that SSMS itself is not opening....Without query analyzer how will I fire the command..?
Post #556359
Andras Belokosztolszki
Andras Belokosztolszki
Posted Thursday, August 21, 2008 3:21 AM
Ten Centuries
Group: General Forum Members
Last Login: Thursday, January 26, 2012 5:26 AM
Points: 1,367,
Visits: 1,585
nairsanthu1977 (8/21/2008)
Hello,
The problem is that SSMS itself is not opening....Without query analyzer how will I fire the command..?
You can use sqlcmd from command line for example. Or run SSMS on a remote computer.
Regards,
Andras
Andras Belokosztolszki, MCPD, PhD
GoldenGate Software
Post #556363
GilaMonster
GilaMonster
Posted Thursday, August 21, 2008 3:59 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 4:30 AM
Points: 37,742,
Visits: 30,021
Some background info on what's happened -
http://sqlinthewild.co.za/index.php/2008/07/23/recovery-model-and-transaction-logs/
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #556372
Ray Mond
Ray Mond
Posted Thursday, August 21, 2008 6:50 PM
Old Hand
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 2:28 AM
Points: 343,
Visits: 1,510
1 -stay calm.
2 - what is your database's recovery model? If it's simple, see 3). For full and bulk-logged, see 4).
3 - two possibilities
3a. you have an old transaction that's still active, that's preventing the log from being truncated, causing indefinite growth. Use DBCC OPENTRAN to determine if this is the case. Take steps to end that transaction (commit, rollback, kill etc). Then use DBCC SHRINKFILE to shrink the log file. May need to do it a couple of times, see
here
for reasons.
3b. there were large transactions that caused the transaction log to grow to such a huge size. If this is going to be common, shrinking the file may not be a good option. If not, run DBCC SHRINKFILE to shrink the log.
4. see 3a) and 3b) for possible reasons (but not the suggested resolutions), also
4a. you have not been backing up your transaction log, hence causing the transaction log to grow indefinitely.
Do you need to make a backup of the current transaction log, perhaps for log shipping purposes, or to be able to perform a point-in-time recovery (note that this would still be impossible if there are minimally logged transactions in the current transaction log)? If yes, you'll need to back it up to disk. Run a BACKUP LOG ... command, folowed by DBCC SHRINKFILE.
If not (and you're very sure of this), run a BACKUP LOG with the TRUNCATE_ONLY option, then follow the suggestions by Hadrian and Andras, especially the part on performing a full database backup.
Ray Mond
TLogInfo
- the only FREE tool to analyse your transaction logs. Download
here
.
SQL BAK Reader
- the only FREE tool to inspect your SQL Server backup files without using SQL Server. Download
here
.
Post #557013
manoj2001
manoj2001
Posted Friday, August 22, 2008 3:01 AM
Ten Centuries
Group: General Forum Members
Last Login: Tuesday, March 12, 2013 11:24 PM
Points: 1,145,
Visits: 225
your log size is in GB while Data file size is in MB, it seems you are not taking backup of log.
if log backup is not necessry for you then use command TRUNATE_ONLY and truncate the log.
hope this will work.
Manoj
Post #557132
Jeremy Brown
Jeremy Brown
Posted Monday, August 25, 2008 7:01 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Friday, April 19, 2013 10:07 AM
Points: 190,
Visits: 244
Just curious, not criticizing at all but...
Wouldn't a question like this be best suited for the administration forum?
I'm seeing a lot of these types of questions being posted in the performance forum.
I know we're all trying to help... Guess its just me being the picky "classification" type of anal retentive DBA again... :D
Post #558098
« Prev Topic
|
Next Topic »
15 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
