Thanks Gail, Clear Explanation!!

Hi MVDBA,

I'll get back the access from my client end on tomorrow. Due to network issue, I'm not able to access now..

Can you help me out of this space issue...

Hi MVDBA,

Yes, My Production log file size is 80 GB..

But now, I don't have access to run dbcc sqlperf(logspace) command in Prod. Server..

So, I've taken the log file size...

We have not taken up the log file back up or truncation of log file so far.

We just leave the database as it is since it was created...:crying:

Hi MVDBA,

Recovery Mode: Full

dbcc sqlperf(logspace) Command output:

Log Size(MB) - 1917.742

Log Space Used (%) - 12.87614

Now, I don't have access to my Production DB, I have taken above said size from...

How would I do the truncate of log whole file?

If I truncate the LOG file, will it cause delete data from any of the table? What would be the problem if I truncate the LOG file?

Yes, Space issues..I've moved the .BAK file to other server after compressing as ZIP file. Please find below metrics

Backup file size (.BAK) : 4.10 GB (after unzip)

After restoring .MDF file...

Do you want me to truncate the LOG file after restoring DB into new environment? or Can we take the DB backup after truncating LOG file from Source DB server?