cancel
Showing results for 
Search instead for 
Did you mean: 

ldf files takes more space after client import failed

Former Member
0 Kudos

Hi Gurus,

I had export client from production server and import into quality server, after some time it was failed due to unavailable space in log file, actually on production server log files having 20GB size and before import in quality server I check same size of log files, but after client import failed, log files take all disk space i.e. 48GB which is total disk drive space, now only 9MB disk space is available. I take full backup and log backup with truncate option mark. but not effect to reduce the log file size. please guide me what I'll doing for reduce the log file size.

Thanks in Advanace

Gokul B. Borse

9881843629

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

hI,

Can you check the following SAP note also..

Note 421644 - SQL error 9002: The transaction log is full

Regards

former_member184473
Active Contributor
0 Kudos

Hello Gokul,

Check the following note:

363018 - File managent for SQL Server

Regards,
Eduardo Rezende

Former Member
0 Kudos

Hi,

The Note 363018 is not available ..... can u pls give me link (URL)

former_member184473
Active Contributor
0 Kudos

Hello Gokul,

I just checked and note 363018 is available. You can use the following link:

http://service.sap.com/sap/support/notes/363018

Regards,
Eduardo Rezende

nicholas_chang
Active Contributor
0 Kudos

Hi,

run command DBCC SQLPERF (LOGSPACE)

if the percentage returns is low, and no data in the log (supposely no, as you've execute the backup & truncate the log) just proceed to shrink it. You can do it via GUI in MSSQL studio.

Cheers,

Nicholas Chang

Former Member
0 Kudos

Thanks I got the link and able to open the note

Former Member
0 Kudos

Hi,

Did you already try the DBCC SHRINKFILE?

http://support.microsoft.com/kb/907511

And export would be log intensive activity, so the log size is increasing. Ideally MSSQL puts logs in auto grow mode. After the export you could shrink the file.

Can try to set recovery model to 'simple'. In database properties/options and set the recovery model to simple.

Regards,

Srikishan

Former Member
0 Kudos

I think DBCC shrinkfile is best solution, may be it'll reduce the log file size.