1 Reply Latest reply on Feb 29, 2016 8:16 AM by cj_bergeron

    Polling detail tables created with the wrong date appended for leap year. ("<>_detail_20160301" instead of "<>_detail_20160229")

    cj_bergeron

      Already submitted a support ticket, but wanted to see if anyone else had the same issue, or knew of a fix.  I noticed today that the NPM detail polling tables have the incorrect date appended to the table name today.  My concerns are that I could lose today's polling data, be off by a day, or otherwise be obscured due to this.  I have already verified that the polling engine as well as the SQL server have the correct time and date.

      leapYear_PollingTableDate_incorrect.JPG