xerxes2985 Posted February 8, 2019 Report post Posted February 8, 2019 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. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted February 8, 2019 Report post Posted February 8, 2019 It means that your collection query is causing the problem. Review the query to fix the problem. Quote Share this post Link to post Share on other sites More sharing options...
xerxes2985 Posted February 8, 2019 Report post Posted February 8, 2019 It happens even when using "direct" and not a query. Quote Share this post Link to post Share on other sites More sharing options...
xerxes2985 Posted February 8, 2019 Report post Posted February 8, 2019 I think I may have found the offender. Testing now. Quote Share this post Link to post Share on other sites More sharing options...
xerxes2985 Posted February 8, 2019 Report post Posted February 8, 2019 @GarthMJ you’re a lifesaver. Looks like my offending collection was trying to look at installed applications, display name, then I had it AND to AI class for Product Version. whatever reason I did that, removing that bad logic fixed it. I owe you lunch sometime, somehow. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted February 8, 2019 Report post Posted February 8, 2019 🙂 I will be at https://mmsmoa.com/ this year.. feel free to look me up. Quote Share this post Link to post Share on other sites More sharing options...
