In SCCM, any time I attempt to update a collection, it causes tempdb to fill up, and eventually causes SQL server to stop working properly. SQL Server databases reside on their own drive, and each time it gets hung on SMS_COLLECTION_AUXILIARY_EVALUATOR. I've specified a 50 GB limit for tempdb and a 30 GB limit for the log db.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
In SCCM, any time I attempt to update a collection, it causes tempdb to fill up, and eventually causes SQL server to stop working properly. SQL Server databases reside on their own drive, and each time it gets hung on SMS_COLLECTION_AUXILIARY_EVALUATOR. I've specified a 50 GB limit for tempdb and a 30 GB limit for the log db.
Any suggestions.
Share this post
Link to post
Share on other sites