-1

I have database in SQL Server, when I create backup the size of backup file is 4 Gb and its data log file shows 136 GB. When I restore the log file size shows 136GB which effect over performance - is there any solution?

Thank you in advance

I googled but did not find solution.

SOHRAB
  • 1

1 Answers1

-1

it's generally okay to shrink the transaction log file after taking a full and log backup if it has grown excessively. However, be cautious when shrinking as it can cause fragmentation. It's essential to monitor your database's size regularly and follow best practices to avoid log file growth.

you can see here

Sumit Patel
  • 1
  • 1
  • you can Check Recovery Model or Avoid Long Transactions –  Oct 02 '23 at 04:57
  • thank you for your quick response ,I executed below command its reduced size to very low and my database is also working, I hope I did not lost my data .

    ALTER DATABASE DatabaseName SET RECOVERY SIMPLE GO DBCC SHRINKFILE (log name, 1) GO ALTER DATABASE log name SET RECOVERY FULL

     – SOHRAB Oct 02 '23 at 10:30