Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics RMS (Archived) / Transaction log fillin...
Microsoft Dynamics RMS (Archived)

Transaction log filling up memory space

(0) ShareShare
ReportReport
Posted on by Manny Sanchez 35

Has anyone come across this scenario: 

Store1 has HQ server.  Store2 in Dr Philips has exceeded its hard disk memory.
The CPU that serves as the server at Store2 appears to be storing transaction logs at:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\Store2_Log

It has maxed out the 74 GB on the CPU.

recently the CPU popped up this message:

"The transaction log for database 'mydatabase' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases"

when that happens the store is unable to enter any new customers and cannot log into the RMS Manager program.

*This post is locked for comments

  • Tara_IE Profile Picture
    Tara_IE 30 on at
    Re: Re: Transaction log filling up memory space

    I ran into a similar issue- not sure its related or not, but its worth pointing out for future reference.  If a new store is created within HQ that is sitting on a full version of SQL Server then restored on a machine running SQL Express, the transaction log will fill rapidly- within a matter of days! Its to do with SQL recovery modes- in SQL Server, the default mode is "Full" while in SQL Express, it's "Simple".  Once the log is cut back using the statements given here already, changing the recovery mode of the SQL Express database using the free SQL Management Studio Express tool will prevent it happening again. 

  • willygreen Profile Picture
    willygreen 50 on at
    Re: Transaction log filling up memory space

     You should set up a maintenance plan on your SQL server to keep this log from getting too big.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: Transaction log filling up memory space
    BACKUP LOG [Your DataBase] WITH NO_LOGUSE [Your DataBase]

    GO

    DBCC SHRINKFILE ('Logical Log File Name', 20) --20 equals size of the log file after shrink and is in MB

    GO

    I would make sure this is done with a full backup otherwise you will not be able to roll back any transaction after you shrink the logs.  

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans