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

[SanjivMeher]

What should be there in the report and do you need only a weeks data or you need all data?

[DaSmith9]

assume more than a week or month, and could be any field on incident including 'u_' fields. I can get the data out into XLSX and massage it and join it there, was hoping for an easier way to do via reporting in the tool. Database view was really what I needed. 

[sachin_namjoshi]

It's not good idea to query sys_email table since this table grows big over time.

You will have performance issues with your report if you query sys_email table.

What's business requirement of generating report on email table?

Regards,

Sachin

[DaSmith9]

Definitely aware of the table size and performance constraints, that's why the table is on rotation to begin with. I'm just curious what creative alternatives in platform there are besides database view. 

Business requirement I think is irrelevant, it's just a "how-to" scenario at this point.