What does one do?

I tried "backup log mb with no_log" to truncate the file.  I've now
started a shrinkdatabase.  I can't backup since the drive is full.  I
can't disconnect because it's 7.

How does one actually reduce the log file size?

thx
md

PS isn't simple logging supposed to avoid this problem?
PSS is it possible to set a DTS to not log?

*** Sent via Developersdex http://www.developersdex.com ***

See if this helps:

INF: How to Shrink the SQL Server 7.0 Transaction Log
http://support.microsoft.com/kb/256650/EN-US/


AMB

Show quoteHide quote

Hi,

Since you dont require the transaction log backup you could truncate the log
first

BACKUP LOG DBNAME with TRUNCATE_ONLY

After that check the log usage by executing DBCC SQLPERF(LOGSPACE)

If the usage is very low than SHRINK the LDF file using DBCC
SHRINKFILE('logical ldf name',size)

Please refer the link Alejandro pointed out.

Thanks
Hari
SQL Server MVP

Show quoteHide quote

I am new to this site, but would suggest a DB backup after you truncate the
log file, just to be safe.

Show quoteHide quote

Also run a DBCC OPENTRAN agains the database in question to make sure there
are no pending transactions to be completed.

The trasaction log architecture is different in SS7.0 versus SS2K and can be
quite difficult to shrink, even when using BACKUP LOG ... WITH NO_LOG or
WITH TRUNCATE_ONLY, which are synonomous by the way.

Usually, you will have to kill all processes but your own within the
database you are concerned with.
Execute sp_detach_db.
Delete the Transaction log file(s) for the database in question.
Execute sp_attach_single_file_db.

The new transaction log will be the size of the transaction log for the
model database.

Also know that regardless of Recovery Model, which didn't exist in
SS7.0-there were database options: 'trunc. log on chkpt.' and/or 'select
into/bulk copy'-EVERY TRANSACTION IS WRITTEN TO THE TRANSACTION LOG.  There
is no way to stop this.  The recovery settings just tell SQL Server what to
do with "COMPLETED" transactions within the transaction log file if they
have not been backed up yet.

If you are using 'trunc. log on chkpt.', then completed transactions are
automatically purged on the next CHECKPOINT process.  This allows you to
write over that freed up space with the next transaction.  However, your
transaction log will grow to support the largest single active transaction
or concurrent set of transactions.

If transactions are open, not completed or rolled back, then new
transactions can not overwrite those regardless of the recovery settings, or
db options, as the case may be.

Sincerely,


Anthony Thomas


I am new to this site, but would suggest a DB backup after you truncate the
log file, just to be safe.

Show quoteHide quote

Problem with osql.exe -L
alter table drop column and dbcc cleantable
Simple Question: What's the best way to duplicate a DB under another name?
stored procedure with different criteria
Server: Msg 7391, Level 16, State 1, Procedure <OBJECT>, Line
SQL7 2 DB files down to one???
varchar vs nvarchar
Autonumber
Removing Identity Property
Query Cost - how is it calculated?