🚀 go-pugleaf

Emil,

I ran into the same problem.  SQL Server doesn't seem to update the size of the
log file when it should.  Trying doing a DBCC Checktable on your syslogs table.
Also if you do a Manage|Database|Properties|Full in the MS SQL Adminstrator you
shoudl get back accurate info about the log size.  I think that doing the DBCC
on syslogs will help SQL Server realize the actual size of the table though.

Allen.

-------------------------------------------------------------------
Allen Greer                      Internet: greeral@ccmail.orst.edu
SIS System Integrator, Info Serv    Phone:          (503) 737-2671
Oregon State University, Milne 202    Fax:          (503) 737-4484
Corvallis, OR 97331-5202
WWW: http://www.bus.orst.edu/faculty/greer/greer.htm

______________________________ Reply Separator _________________________________
Subject: SQL Server LOG file Problem
Author:  Microsoft SQL Server Discussion List
<MSSQL-L%DUKEFSB.BITNET@VTBIT.CC.VT.EDU> at Internet_gateway
Date:    4/2/95 11:17 PM


Following is the Properties List of my database BLBDATA.  No matter how hard
we tried, the Log Space Used is still as big as 270Mb!  I did try using Dump
Database, Dump Transaction with truncate and with no_log but still does not
help.  The Log used to store together with the data segment master, I tried
to altered it to the new device LogDev but doesn't help neither.

Could anybody help?

Database Properties: BLBDATA on BLBHK_S1 as of 04/03/95 11:52:23
Number of Users: 1
Number of Groups: 1
Options Set: no options set
Reserved Space: 275098 KB
Data Space Used: 274502 KB
Log Space Used: 271520 KB
Index Space Used: 132 KB
Unused Reserve: 464 KB
Unused Log Space: 8 KB

Device                              Size
Usage

LogDev                              100 MB
log only
master                              250 MB
data only
master2                             300 MB
data only

TIA.

Cheers:)

Emil Chan
emilchan@asiaonline.net