>>>Take a look at TRUNCATE LOG in SQL Server Help.
>>>
>>>>Hi all:
>>>>
>>>> When I run a nightly batch, I notice in the SQLdata directory that an MDF file is created that records the logs of transactions that occur while my transaction was running. This MDF file can be very big. Is there a way that I can prevent this MDF from being created or is there no way to prevent it?
>>>>
>>>>Thank you.
>>
>>AFAIK truncating the log will affect the LDF file, not the MDF. Also is TRUNCATE LOG a SQL Server 2000 command? There is no such command in SQL7.
>
>You are right, it will only affect the LDF file.
>
>The command to truncate the Log file exists in SQL 7 as well. Yet, I don't remember the exact name :( - I always used it from the Enterprise Manager. I haven't check SQL 2000.

Hector, I checked the 7.0 BOL and didn't see a -command- to truncate the log file. There was, however, a SQL-DMO method called Truncate() and two SQL-DMO properties called TruncateLog and TruncateLogOnCheckpoint that seemed to do this. There was also a database option called trunc.log on chkpt. that seemingly needed to be set for a database to be "eligible" for log truncate mode.

But, like you, I always use(d) the EntMgr (sigh)...