Async Server Message Database Maintenance Plan

(0) Share

Report

Posted on by Community Member

Good day.

Hi Experts,

May I ask your opinion on how I will maintain the Async Server message database. Currently, it is around 60GB in size in running around 2 and a half year. Do you have any idea how will I maintain these? Is it okay if I will create a new MSG DB and remove the previous one? What would be the risk if I do it?

I hope you can give me some ideas.

Thanks,

Raph

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (1)

Suggested answer

Mahmoud Hakim 17,887 on at

Like (0)

Report

try to make periodically Maintenance like update statics, reindex, clear log,

https://www.targetprocess.com/guide/installation/database-maintenance-recommendations/

www.officetools.com/.../database-maintenance-explained

blogs.msdn.microsoft.com/.../database-maintenance-strategies-for-dynamics-ax

Was this reply helpful? Yes No
Suggested answer

Mea_ 60,284 on at

Like (0)

Report

Hi Raph Dumape,

There are multiple HFs available to cleanup different retail DB and improve performance like:

fix.lcs.dynamics.com/.../Resolved

fix.lcs.dynamics.com/.../Resolved

So you may consider to install this 2 and look for other relevant to your problem or update to latest CU available.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Mahmoud,

Thank you for this. But what I need is very specific with the Async Server message database. Is it safe to compress it (File data compaction)?

Thanks,

Raph

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Ievgen,

Thank you for this. I might use this in the near future. But what I need at the moment is the Async Server message database as it keeps on growing. What would be the indications/risk if I delete the older data? That's what I am looking for to lessen the file size of the database.

Thanks,

Raph

Was this reply helpful? Yes No
Suggested answer

Mahmoud Hakim 17,887 on at

Like (0)

Report

Hi Raph Dumape

compress database is safe for any database , and recommend for large size databases

Compressing data reduces database storage, which leads to fewer I/O reads and writes. However, SQL Server consumes more CPU resources when it compresses and decompresses data.

Was this reply helpful? Yes No
Suggested answer

Hassan_rulz 3,801 on at

Like (1)

Report

Hi Raph,

You can delete older download and upload logs from AsyncServerMSG dbs as these are just logs and consuming storage space.

Table names:

DOWNLOADSESSIONDATASTORELOG

UPLOADSESSIONLOG

Regards,

Hassan

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Hassan,

Did you do this before? What would be the repercussion if we did this?

Thanks,

Raph

Was this reply helpful? Yes No
Suggested answer

Hassan_rulz 3,801 on at

Like (2)

Report

Hi Raph,

There is no repercussion as these are just msgs log which we dont need or mandatory.

I have done this and face no repercussion.

For your satisfaction, you can delete all the logs except for current month (September 2017).

Regards,

Hassan

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Hassan,

This is very informative.

I just want to clarify if we delete all the logs from the msg DB, does it will affect our pulling process (Pulling transactions from store)? Because sometimes we tend to re-pull all transactions from start to present. I hope you get my point.

Thank you for answering my question. God bless us all.

Raph

Was this reply helpful? Yes No
Verified answer

Hassan_rulz 3,801 on at

Like (0)

Report

Hi Raph,

It will not effect anything as it will create new logs when it will pull job. These are just working logs and nothing else.

Regards,

Hassan

Was this reply helpful? Yes No