Category ""
ADVERTISING
What is the LDF file in SQL Server? what is its purpose? can I safely delete it? or reduce its size because sometimes it's 10x larger than the database file mdf.
To know what transactional detail kept in a .ldf file you can try SQL .ldf file viewer which is able to open, read and analyze all the information related SQL database transactions.
Sql Server LDF file taking too large space Asked 6 years, 6 months ago Modified 1 year, 7 months ago Viewed 61k times
So I have been neglecting to do any backups of my fogbugz database, and now the fogbugz ldf file is over 2 and half gigs. Thats been built up over the six months we've been using fogbugz. I backed up the database, then I backed up, and truncated the transaction log, yet the transaction log is still 2 and a half gigs.
I need to empty an LDF file before sending to a colleague. How do I force SQL Server to truncate the log?
And remember, never ever under any circumstances delete the log (LDF) file! You will pretty much have instant database corruption. Cooked! Done! Lost data! If left "unrepaired" the main MDF file could become corrupt permanently. Never ever delete the transaction log - you will lose data!
To reattach in SSMS Right Click Databases --> Attach. It might complain that it can't find the MDF/LDF because the internal settings are still pointing to the old, but you just have to repoint the LDF/MDF to the renamed files in the popup GUI.
Reason: 15105) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation. Cannot close event log because there are still event handle users active.
The transaction log remained large. I backed up the transaction log then proceeded to shrink the transaction log .ldf file. However the transaction log did not shrink at all. I then issued a "CHECKPOINT" followed by "DBCC DROPCLEANBUFFER" and was able to shrink the transaction log .ldf file thereafter
The machine was restarted while I was shrinking a database and since then the SQL Server (MSSQLSERVER) not starting. After reading the blogs I replaced the master.mdf and mastlog.ldf files from the