Yeah this must be one heck of a hidden gem. It did not show up in the query I listed below because our primary had apparently never ran it. It also didn't show up with intellisense in SSMS. Once I actually executed it, it showed up everywhere, but I wouldn't have been able to find it otherwise.
Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Wednesday, September 02, 2015 12:49 PM To: [email protected] Subject: RE: [mssms] Stored procedure dbo.CH_SyncClientSummary It was just there, they didn't have me create it. I don't have the ones you listed. Hmm... From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Wednesday, September 2, 2015 9:18 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Stored procedure dbo.CH_SyncClientSummary Yeah that's what I meant by SSMS. Still find it interesting you have that SP and I don't. Most of the native SPs start with spXXXXX. Any chance this is a SP Microsoft had you create as a workaround? Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Wednesday, September 02, 2015 12:13 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Stored procedure dbo.CH_SyncClientSummary I'm doing this in SQL Management Studio. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, September 1, 2015 3:37 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Stored procedure dbo.CH_SyncClientSummary That's weird, I don't have that as either a SP or a view. [cid:[email protected]] You literally open up SSMS, type that in the query window, and execute? Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Tuesday, September 1, 2015 5:30 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Stored procedure dbo.CH_SyncClientSummary Neither of those. I ran dbo.CH_SyncClientSummary. When I run that manually, the HW & SW inventory date updates in the console. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, September 1, 2015 1:53 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Stored procedure dbo.CH_SyncClientSummary Just playing around, found a query that gives you the last run time of a SP. Which one is the SP you are running? spUpsertCH_ClientSummary? spUpsertCH_ClientSummaryHistory? Another one? SELECT o.name, ps.last_execution_time FROM sys.dm_exec_procedure_stats ps INNER JOIN sys.objects o ON ps.object_id = o.object_id WHERE DB_NAME(ps.database_id) = 'CM_CAS' ORDER BY o.name Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Tuesday, September 01, 2015 4:51 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Stored procedure dbo.CH_SyncClientSummary Hardware inventory every 7 days? Software inventory sure if you even need it at all but I've always ran hardware inventory every single day. I mean 7 days is fine if you can live with old data but if you want more real-time info do it once per day. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Tuesday, September 1, 2015 3:44 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Stored procedure dbo.CH_SyncClientSummary This is correct. I have inventory set to run every 7 days (per Microsoft's recommendation - I think I should set it more frequently, but for the sake of the open case with them, I'm keeping it at 7 for now). From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Tuesday, September 1, 2015 1:29 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Stored procedure dbo.CH_SyncClientSummary Yes, but things like inventory times in the console are fed from v_CH_ClientSummary and I *think* that there is a logic piece that if the last hardware scan is greater than the refresh interval then the console does not display correctly From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: 01 September 2015 21:00 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Stored procedure dbo.CH_SyncClientSummary Also, this is a ClientHealth (indicated by the CH prefix) view so really would have no impact on inventory info displayed in the console. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Tuesday, September 1, 2015 3:54 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Stored procedure dbo.CH_SyncClientSummary Hi Mike Are you running inventory on a daily basis? Try setting this to no more frequently than 4 days AFAIK this SP runs every 24 hours From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: 01 September 2015 20:48 To: [email protected]<mailto:[email protected]> Subject: [mssms] Stored procedure dbo.CH_SyncClientSummary My HW/SW inventory is only updating in the console when I manually run this stored procedure. I've been working with MS support, and the tech there said this procedure only runs once a month, so I will not see this data update until it runs one month from now. This rings false to me. Is he wrong? Best Regards, Mike Murray Desktop Management Coordinator - IT Support Services California State University, Chico 530.898.4357 [email protected]<mailto:[email protected]> ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
