I have 2 databases in my development server when i switch to Demodatabase the code is publishing easily but when i switched to the database that is copy of production server database after restarting the business central its publishing the code but the second time its not publishing after doing some research i got know that due to database size some sql process are stuck in the backend due to which the publishing process to onprem business central is stuck so guide me what can i do
DARLiveBK is the production server database copy that is not letting me publish the code
this is the database memory information and below is the research problem
while using the DARLiveBK database these are the process that are stuck that seems to be the problem causing to publish the code
Your issue is caused by SQL Server memory pressure on a small (7 GB RAM) dev server when using a prod-sized database copy: during extension publish, SQL needs large memory grants, hits RESOURCE_SEMAPHORE, and publish gets stuck after the first run. The root problem is SQL max memory set to unlimited, which starves either SQL or the Business Central service tier over time. Fix this by limiting SQL max server memory to ~4–5 GB, restarting SQL, and ideally increasing server RAM to 16 GB+. Also stop Job Queue/users during publish, and if needed temporarily set the DB to SINGLE_USER WITH ROLLBACK IMMEDIATE to clear blocking. After restoring prod DBs, always update statistics and check tempdb, as bad stats + large DBs worsen memory grants. This is a capacity issue, not a BC bug.
Regards,
Oussama Sabbouh
Was this reply helpful?YesNo
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.
282
Share
Report
All responses (
Answers (
