Solved

Clearing Space Used By .LDF files

Posted on 2003-11-13
9
295 Views
Last Modified: 2012-06-27
There is a data warehouse running on SQL Server 2000. During migration I see that Warehouse_Log.LDF has become 5+ GB in size. I did a checkpoint in Query Analyzer and shrank the database from the enterprise manager and yet this value does not go down in size.

What can I do to free up this space

Thanks

Shariq
0
Comment
Question by:shariq
9 Comments
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 9743757
Please maintain your open questions:

1 04/23/2003 50 Output Table Data Into Fixed Length Form...  Open 3rd Party Applications and Development Tools
2 09/09/2003 75 Convert From Oracle to MS-SQL  Open Microsoft SQL Server

Thanks,
Anthony
0
 

Accepted Solution

by:
kauf earned 50 total points
ID: 9744029
Hello Shariq,
If it is a secondary Transaction log you can resize / delete it by:
BACKUP LOG [DatabaseName] WITH TRUNCATE_ONLY

And then modifing the data in enterprise Manager.
i once tried to shrink a primary file, but only was able to do this through detaching and attaching the database.
0
 

Expert Comment

by:kauf
ID: 9744038
Ah yes, first - check that you've not checked automatically grow in the transaction log options to prevent even more size...
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 3

Assisted Solution

by:htarlow
htarlow earned 50 total points
ID: 9744060
If the database recovery type is full or bulk logged, backup the logfile to shrink it.
0
 
LVL 34

Assisted Solution

by:arbert
arbert earned 50 total points
ID: 9750158
"grow in the transaction log options to prevent even more size... "

agree with the above suggestions to backup with truncate_only and then shrinking the log file.  HOWEVER, I would not suggest you turning the auto grow off opn the logfile--just bite you in the butt later when you have big inserts or updates....
0
 

Expert Comment

by:kauf
ID: 9752767
in an emergency case, you can set a temporary (secondary) transaction log anytime (this you can delete after BACKUP LOG... w/o problems)
0
 
LVL 34

Expert Comment

by:arbert
ID: 9752863
"in an emergency case, you can set a temporary (secondary) transaction log anytime (this you can delete after BACKUP LOG... w/o problems) "


why go through the extra effort.  MS SQL Server best practices say that the log file should be set to auto grow....
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Let's review the features of new SQL Server 2012 (Denali CTP3). It listed as below: PERCENT_RANK(): PERCENT_RANK() function will returns the percentage value of rank of the values among its group. PERCENT_RANK() function value always in be…
Introduction In my previous article (http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/A_9150-Loading-XML-Using-SSIS.html) I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.
Viewers will learn how the fundamental information of how to create a table.

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question