Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Improve automatic SQL configuration, tuning, and maintenance of the SCCM DB & SQL Server

Current architecture around SCCM’s management of SQL configuration and maintenance is old and hard to use. It requires a lot of manual oversight, and manual SQL tasks. And the default SQL settings created by SCCM are non-optimal. SQL is a powerful beast. Rethink ways SCCM can use it better, and keep it more optimally tuned and configured. Rethink how to run maintenance and backup tasks without downtime or impact to the production sites and deployments (this especially becomes more important with features like Conditional Access, that can never really have downtime.)

146 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Admindjam (Product Director, or Executive, System Center Configuration Manager) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
Noted  · 

5 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Garrett Marsh commented  ·   ·  Flag as inappropriate

    100% agree with this, SCCM and SQL should match what a CM RAP or SQL RAP would tell us to do and make the system perform better, multiple Temp DB's, Auto Growth on Temp DB, Optimize AD HOC queries, indexing, corruption check, DBCC, etc....

  • Steve Thompson commented  ·   ·  Flag as inappropriate

    I'd like to see tempdb and CM database files be properly created and sized depending on the estimated client count.

  • Steve Thompson commented  ·   ·  Flag as inappropriate

    Completely agree! Consider adding in Ola Hallengrens index and statistic optimization scripts to tune CM and SUSDB...

Feedback and Knowledge Base