Scheduler Mystery

I have a scheduled job that executes sql to dump tran with no log. I have i
t
running at night so no users are affected. The next morning the job says it
succeded with no errors accounted for. However I have checked the size of
the ldf and it is huge. Our server space is getting smaller and smaller
every day, so I am suspect that the log file is not being truncated. When I
checked the SQL server event viewer, it shows an Error application event whe
n
the truncate process is started. Can anyone tell me why the scheduled job
shows a successfull run, while the event viewer tells another story?What version of SQL Server?

>I have a scheduled job that executes sql to dump tran with no log.
As of 7.0, we use BACKUP instead of DUMP, but DUMP is still allowed. Anyhow,
this doesn't shrink
physical file size. Are you doing regular transaction log backups? If nor, u
se simple recovery
model. If you are, don't just cut the log as it will break the log backup se
quence.
As for shrinking the file size, I've listed a number of articles in this art
icle:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Toco" <Toco@.discussions.microsoft.com> wrote in message
news:723A119C-5D64-4C36-9865-9BD8FBAF2775@.microsoft.com...
>I have a scheduled job that executes sql to dump tran with no log. I have
it
> running at night so no users are affected. The next morning the job says
it
> succeded with no errors accounted for. However I have checked the size of
> the ldf and it is huge. Our server space is getting smaller and smaller
> every day, so I am suspect that the log file is not being truncated. When
I
> checked the SQL server event viewer, it shows an Error application event w
hen
> the truncate process is started. Can anyone tell me why the scheduled job
> shows a successfull run, while the event viewer tells another story?