Microsoft
Software
Hardware
Network
Question : Shrinkfile and backup log with truncate only do not shrink log
Hi,
The log file will not shrink in size.
I used the following commend (to no avail):
CHECKPOINT
GO
DBCC shrinkfile('DBNAME', 1)
GO
BACKUP LOG CAM WITH TRUNCATE_ONLY
GO
DBCC shrinkfile('DBNAME', 1)
GO
The dabase was imported from 2000 a few weeks ago.
It is using the "FULL" recovery model, since it is a high availability system.
When I run SP_LOCK, I see no locking transactions.
When I run the DBCC opentran, I see the following:
Transaction information for database 'DBNAME'.
Replicated Transaction Information:
Oldest distributed LSN : (0:0:0)
Oldest non-distributed LSN : (145792:201:1)
But there is no replication on this database... And there hasn't been since I got here (1 year+).
I also ran the:
EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
But I got the message:
Msg 18757, Level 16, State 1, Procedure sp_repldone, Line 1
Unable to execute procedure. The database is not published...
Any ideas?
Answer : Shrinkfile and backup log with truncate only do not shrink log
You should look at
http://support.microsoft.c
om/kb/9075
11/en-us
and remember that log files are circular. If you have a 1 GB of log file, it will shrink it to the point in the log that is free to the end of the file.
Random Solutions
wordpress theme previewer?
Optimizing Oracle 10g, recently upgraded from 8i
Rails and Flash Filereference - receiving HTTP 422
OWA Page cannot be displayed after login - loads frames
How to copy security settings from one server to another in SQL 2005
Cannot sync calendar items from Exchange to PDA
conver .gfx graphics for MSword
Store PDF file into Database using BLOB Datatype
Windows, Linux and network real time monitoring tools.
Can't mount database after power failure