Reporting against sys_email

[DaSmith9]

Had a reporting scenario come up and wanted to see how or if anyone has ever handled this. 

Scenario is to report against 'sys_email' and 'incident' and be able to filter for emails against certain incident criteria. A database view was my first thought, but I discovered database views cannot be configured against tables in rotation, which 'sys_email' is. Also, adding 'sys_email' to the system properties to be able to report directly against it is not viable as you cannot dot walk to the incident table (that I could find) to bring in incident data for filtering against.

Is this an exercise to query separately and join outside of ServiceNow, or maybe into a staging table that could be reported on? 

Thanks,
Daniel

[Giles Lewis]

I do a lot of ad-hoc analysis of ServiceNow emails, both sent and received, using SQL.  I have 1.5 million emails in a MySQL database. This allows me to join to task or incident and write complex queries that would be impossible in ServiceNow.  And it is fast.  Obviously the initial export took many hours, but now that I have it I can update it pretty quickly. We do about 3500 emails/day. I use https://github.com/gflewis/sndml3/, but you could also use SnowMirror.  However, if you need a ServiceNow report then I would probably try adding a reference field to sys_email, or the solution suggested by Michael Ritchie.