If I'm already in the console and I don't need 100% update data then the console is fine. But if I'm not in the console or that I need 100% up to date data them the reports will be faster/better.
Doing it more often will clearly impact performance. The real issue is do you care? IMO for 2000 computer if you see any performance issues running the summarizer more than once every 24 hours then you have much bigger problems. Just my two Canadian cents. :) From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, December 31, 2014 7:26 PM To: [email protected] Subject: RE: [mssms] Summarization - Collection in console I'm not saying I wouldn't use the reports, but it is easier and faster to see some basic information while I'm already in the console and the collection instead of opening a report. If I know it's a day behind, everything below may worth a look into. The same record now updated after 2 days. That probably could be speed up. We may only have max 2000 clients, doing anything more often shouldn't impact performance but make that actually useful. -R From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Garth Jones Sent: Mittwoch, 31. Dezember 2014 17:41 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Summarization - Collection in console I'm unclear as to why you wouldn't use reports. Report will ALWAYS be 100% update date, the console will be up to 24 hours out of date as the data is summarized, in order to allow the console to be fast. IMO you should NEVER use the console for anything except for creating collection and deploying software. It is just not as efficient as the reports. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, December 31, 2014 10:37 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Summarization - Collection in console Because it's not the same thing and having data in that view but not being accurate would make it useless. I have the same question with clients showing 29.12. as scan date, but there is inventory from today (31th), hence the question, where is that data coming from and what would update it? -R From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Garth Jones Sent: Mittwoch, 31. Dezember 2014 15:51 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Summarization - Collection in console Why wouldn't you use a report for this? What exactly are you trying to do? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of sccmfun Sent: Wednesday, December 31, 2014 9:17 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Summarization - Collection in console Does anyone know how to force summarization so you can see up-to-date info such as HW inventory scan when looking at machines in a collection. If you look at a collection of machines and select the different columns, one of them being hardware inventory, the data is outdated. I know this view is based off summarization, but don't know what the summarization schedule is or how to kick it off manually. I searched for the stored proc, but no luck. I'm also confused as the summarization for the policy requests column seems to update more frequently, but doesn't look like the hardware or other info is updated as quick. I would assume it's one stored proc that updates everything, but then wouldn't all columns update and not just the policy request? Any info on this is appreciated. Happy New Year!
