Wondering if anyone is using this in a production environment. I have roughly 11,000 sensors. And am struggling to get this to export to SQL?

What set are you using to get this done ? Thanks

Article Comments

Hi,

What exactly do you want to export?


May, 2015 - Permalink

advanced reporting, say a weighted server report, we have a reporting department that writes all our reports and would be able to leverage a lot more of PRTG


May, 2015 - Permalink

What exact problems do you experience? Long execution time?


May, 2015 - Permalink

yeah, that's really the only issue I have, is long execution....yesterday I did a robo copy of the datastore for PRTG to a dedicated server, disabled the probe service and started it again to see if I could cut it down.......in the previous attempt I was using 4 vm servers, processing 2500 sensors and it took each one 15 hours to complete.


May, 2015 - Permalink

That's actually one of the problem the tools has with larger installations. We're aware of it and trying to improve the extractor in the future. Although this might take a while, I'm afraid :/


May, 2015 - Permalink

This article applies as of PRTG 24

if you are looking for data extraction from PRTG to SQL / Oracle database, try the PRTG extension: PRTG Data Extractor.

There is a trial version available on the Paessler website

Main features:

  • supports PRTG Enterprise Monitor
  • export from multiple PRTG servers into 1 database
  • export to any number of DBs you need
  • export to MSSQL or Oracle (more DBMS types coming)
  • continuous automatic exporting to keep SQL data in sync
  • smart sensor filtering to automatically include new sensors in export
  • and more...

Feel free to contact the PRTG custom service team if you have any questions.


Feb, 2020 - Permalink