25 авг. 2011 г. · Here is a solution to reduce the physical size of the transaction file, but without changing the recovery mode to simple.

30 дек. 2016 г. · 1) Switch to Simple Recovery Model · 2) Run a CHECKPOINT and DBCC DROPCLEANBUFFERS (just in case) · 3) Shrink the log file · 4) Switch back to Full ...

30 сент. 2014 г. · You can temporarily set recovery model to simple and truncate log. You also need to find the long running transaction that is active and find the root cause.

2 сент. 2008 г. · For SQL Server 2008, the command is: ALTER DATABASE ExampleDB SET RECOVERY SIMPLE DBCC SHRINKFILE('ExampleDB_log', 0, TRUNCATEONLY) ALTER DATABASE ExampleDB ...

6 мая 2009 г. · I did a shrink on the log file and its still 2 and a half gigs. Nothing I do seems to shrink the file in size. Is there anyway to fix the problem?

11 сент. 2008 г. · Back up the log with TRUNCATE_ONLY option and then SHRINKFILE . · Detach the database, delete the log file, and re-attach. · Use the "shrink ...

9 июн. 2022 г. · Don't shrink the whole database. It is too imprecise. Always target the individual file. I.e., use DBCC SHRINKFILE.

4 дек. 2013 г. · ALTER DATABASE myDatabaseName SET RECOVERY SIMPLE; GO -- Shrink the truncated log file to 1 MB. ... How do I shrink my SQL Server Database?

6 мая 2014 г. · To shrink a log file, use DBCC SHRINKFILE (wslogdb70_27_log, X) where X is the target size in MB. Take care not to shrink the log too much, it needs some free ...

6 авг. 2009 г. · Kill the transaction and shrink your db. Close the connection where you executed that query and restart SQL Server Agent (or just the Reader ...