My idea is to humbly request an Identity column for the CustomPollerStatistics_Detail table.
Our company uses Splunk as our Big Data application with Solarwinds used on a smaller (no pun intended) scale. Also, we have other numerous applications that use some type of relational database (MS SQL Server, Oracle, etc.). Splunk has an application named DBConnect that can be used to ingest historical/log data from relational databases using a data input type called "Rising Column". If you are unaware, a "Rising Column" data input functions based on a table having a column with a "rising value". Ideally, the "rising value" should be unique for each record to the Splunk DB connect application. While a "Rising Column" can be a timestamp (datetime) datatype, a timestamp column does not always have unique values (i.e. multiple records INSERTed into a table with one transaction) which can/will causes issues for ingesting data into Splunk. As you may know, an Identity column is a numeric datatype with the value auto incrementing with each INSERT into a MS SQL Server table.
I am aware of the "SolarWinds Add-on for Splunk" app, but it has less features than the Splunk DB connect application. It uses the Solarwinds API which appears to not have any additional features for the issue of ingesting historical/log tables without an Identity column.
