http://blogs.technet.com/jonathanalmquist/archive/2009/04/25/top-10-events.aspxThis will return the top ten events collected. FYI – Given the sheer number of events collected and stored in the OperationsManager database, this query may take a minute to return results. $array = @();foreach ($number in Get-Event | foreach-object {$_.get_number()})en-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.technet.com/jonathanalmquist/archive/2009/04/25/top-10-events.aspx#3230497Sat, 25 Apr 2009 19:26:03 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3230497dmuscett<P>a minute?</P> <P>Get-Event simply gets ALL events in the OpsDB. your loop will load them into an array... for the purpose of sorting/grouping,etc...</P> <P>I have tried this simple approach a while ago <A href="http://www.muscetta.com/2008/01/25/looking-at-opsmgr2007-alert-trend-with-command-shell/" target=_new rel=nofollow>http://www.muscetta.com/2008/01/25/looking-at-opsmgr2007-alert-trend-with-command-shell/</A></P> <P>Powershell IS very cool, but for this type of bulk extraction you should really go TSQL...</P> <P>I have seen this thing throwing an OUT OF MEMORY exception even on SMALL environments with just 50 agents and the default grooming of 7 days...</P>http://blogs.technet.com/jonathanalmquist/archive/2009/04/25/top-10-events.aspx#3230508Sat, 25 Apr 2009 20:29:16 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3230508jtalmquist<P>Yes. &nbsp;I believe you there. &nbsp;Initially, I didn't post any get-event cmdlets, because of the issue you describe. &nbsp;But, I want the main&nbsp;reference table to be complete. &nbsp;So there it is...the get-event cmdlet in use. :-)</P>