You must be aware that

There is a risk on the production database
If you set the recovery mode to simple or bulk logged.

In a production database ,you should

Be using full log recovery mode to

Secure all transactions.

Simple and bulk logged will not 'noted' down

All transactions, if there is a server crash,

And there was not a full backup prior to the crash,

And the LDF file is corrupted.

Then you are running the risk of losing some transactions.

simon qu

MCSE 2003,MCTS 2005,MCDBA 2000,CCNA


-----Original Message-----
From: Crafford R. (Ruan) [mailto:mssqldba-ezmlmshield-x2047000.[Email address protected]
Sent: Monday, 24 December 2007 6:36 PM
To: LazyDBA Discussion
Subject: Large Transaction Log

Hi all,

We have a database of 95Gig and the transaction log is 200Gig (using
SQL2000), the server is running out of disk space, i want to know if its
safe doing the following: Take the database offline, make a full backup,
then detach the database and stop the MSSQL service, then delete the log
file, then attach the data file after which a new log will automatically
be created. Is it safe doing this???


Thank you
Ruan

********************
Nedbank Limited Reg No 1951/000009/06. The following link displays the names of the Nedbank Board of Directors and Company Secretary. [ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ]
This email is confidential and is intended for the addressee only. The following link will take you to Nedbank's legal notice. [ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************


---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html


MS Sql Server LazyDBA home page