Very Computer

Error:
The file 'coost3_logE' cannot be remove because it is not empty.

Now I
backup log coost3 with truncate_only
backup database coost3 to disk = 'e:\coost3.bak'
dbcc loginfo(coost3)

shows many rows (20-30) with status "0" but one that status auf file 3 is
"2"
Itzik Ben-Gan writes in NG that means file is in use.

Why doesn't truncate the log file with backup and backup log and EM truncate
log?

You also have to produce log records to move this active file off that log
file (and onto the other log file). This can be done by doing (dummy)
updates/inserts/deletes.

--
Tibor Karaszi
MCDBA, MCSE, MCSD, MCT, SQL Server MVP
Cornerstone Sweden AB
Please reply to the newsgroup only, not by email.

Quote:> Alter database coost3 remove file 'coost3_logE'

> Error:
> The file 'coost3_logE' cannot be remove because it is not empty.

> Now I
> backup log coost3 with truncate_only
> backup database coost3 to disk = 'e:\coost3.bak'
> dbcc loginfo(coost3)

> shows many rows (20-30) with status "0" but one that status auf file 3 is
> "2"
> Itzik Ben-Gan writes in NG that means file is in use.

> Why doesn't truncate the log file with backup and backup log and EM
truncate
> log?