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
Using Office 2007 in Windows Terminal Services 2003
DNS / MX record config problem? Diagnostic-Code: smtp;554 5.7.1 <
[email protected]
>: Relay access denied
I do not understand which driver install for Hauppauge WinTV PVR TV Tuner Driver
Remove ticks from Excel sheet
How to create a Internet shortcut icon
Backup Exec. won't run backup
What is the optimal six disk configuration for Exchange 2007?
How do I interact with loadMovieNum
using inotify with python
prevent c$ shareing for administrator