Shrink AxDB SQL transaction log

Recently the database transaction log of my D365F&O development environments grew too large and the service was down. When the service goes down all of a sudden, I troubleshoot by restarting the Batch service in dev environment first. If it doesn’t restart, then it is an alarm to turn our focus on latest code changes, model or build issues etc.

Event Viewer is my trustworthy friend is…

Continue Reading AnithaEswaran’s Article on their blog

Shrink AxDB SQL transaction log

Recently the database transaction log of my D365F&O development environments grew too large and the service was down. When the service goes down all of a sudden, I troubleshoot by restarting the Batch service in dev environment first. If it doesn’t restart, then it is an alarm to turn our focus on latest code changes,…

Blog Syndicated with AnithaEswaran’s Permission

Author: Anitha Santosh

Share This Post On
Share via
Copy link
Powered by Social Snap