Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Database Growth after CMG Creation

  • Thread starter Thread starter Ickis99
  • Start date Start date
  • Replies Replies 5
  • Views Views 5K
Status
Not open for further replies.

Ickis99

New Member
Messages
3
Solutions
1
Reaction score
1
Points
3
I have seen at several Configuration Manager Installations, that after the Configuration of a new Cloud Management Gateway, the CM Database starts continually growing. Looking at the Top Tables Report in SQL, the culprit is the dbo.SCCM_Audit Table with tenthousands of Similar entries referring to the new CMG.

None of the default Maintenance Tasks of SCCM seems to delete old Audit Entries. My question is, is it safe to implement a Script that deletes these entries directly in the SQL Table (at least entries older than 60 days or something like that) or is there a better solution for this problem?

Most Constellations where i have seen this are already on 2111 with Rollup and the CMG is already Virtual Scale Set but it seems like there is the same problem with classic CMGs.

Thank you.
 
Solution
Hello! In the end MS acknowledged, that this is indeed a SCCM Bug and will be fixed in a future release. I hope it will be included in the 2207 Summary of changes, which will be released soon, but who knows?

In the meantime i execute a weekly script at my affected customers SCCM Database, essentially deleting these entries, which are older than 60 days

delete from SCCM_audit where tablename=N'Azure_Service' and DATEDIFF(day,getdate(),ChangeTime) < 60

I hope this helps.
Yes, this is a known thing and I had seen this happening in my lab too. Now, I would suggest you log case with Microsoft support as you introducing changes to DB is not recommended.
You may run that script but again it is better if the confirmation comes from MS support.
 
Thank you. At least i am not the only one with this problem. I guess i will open a case to be safe.

Maybe the fix will even be included in the Summary of changes for 2203 if i´am really lucky.
 
Hello! In the end MS acknowledged, that this is indeed a SCCM Bug and will be fixed in a future release. I hope it will be included in the 2207 Summary of changes, which will be released soon, but who knows?

In the meantime i execute a weekly script at my affected customers SCCM Database, essentially deleting these entries, which are older than 60 days

delete from SCCM_audit where tablename=N'Azure_Service' and DATEDIFF(day,getdate(),ChangeTime) < 60

I hope this helps.
 
Solution
Status
Not open for further replies.

Forum statistics

Threads
7,157
Messages
27,937
Members
18,239
Latest member
rajg
Back
Top