can access to solarwinds database for a third party tool cause any issue for the app performance (Tool to used to fetch the data from DB).
Anything that requests data from the database does put load on it. I've brought solarwinds to their knees running poorly thought out queries in the past. Just depends how much data you are trying to extract and how often.
Disclaimer:The content posted herein are provided as a suggestion or recommendation to you for your internal use. The information set forth herein may come from third party website or customers. SolarWinds is not liable for any downtime or any issue that may occur if you perform the following suggestions on the link provided. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.Please try this first in a lab environment, before implementing to your production.You can open a support ticket to get insights, but please take note of our Working with Support Policy, customizations are not supported especially if this would involved custom scripts or queries, support can assist in a best effort practice since our support team is intended as a break fix support.
This is possible, direct access to the SolarWinds database by a third-party tool (e.g., using ODBC or direct SQL queries) can cause performance or stability issues, especially if not handled carefully. Here’s a breakdown of potential impacts and best practices:
Unoptimized or frequent queries can put significant load on the SQL Server hosting the SolarWinds database.
Long-running or poorly indexed queries may:
Cause lock contention or blocking.
Increase CPU and memory usage.
Slow down core SolarWinds modules (e.g., polling, alerting, reports).
If the third-party tool performs SELECT with locks (e.g., no NOLOCK), or worse, uses UPDATE/DELETE, it can:
SELECT
NOLOCK
UPDATE
DELETE
Block SolarWinds from writing performance or configuration data.
Delay or corrupt real-time data ingestion.
SolarWinds does not support or guarantee integrity if data is pulled directly from the database (especially via INSERT/UPDATE).
INSERT
It may also break compatibility during upgrades or patches due to schema changes.
Direct DB access opens a sensitive surface for:
Credential leaks.
Data exposure (e.g., SNMP community strings, credentials in settings).
Unauthorized data extraction if the third-party tool is compromised.
SolarWinds provides a read-only, performance-friendly API via:
Orion SDK: Uses SWIS (SolarWinds Information Service).
SWQL (SolarWinds Query Language): Similar to SQL but safe and optimized.
No locking, minimal performance hit, schema-stable.
Tools can call this via REST API or PowerShell.
SolarWinds SDK GitHub (Official)
If you must access the DB directly:
Only use SELECT queries.
Use WITH (NOLOCK) to avoid blocking.
WITH (NOLOCK)
Throttle query frequency (no faster than every 5–10 minutes unless justified).
Avoid querying large tables (e.g., AlertHistory, Events, ResponseTime_CS) without time filters.
AlertHistory
Events
ResponseTime_CS
Monitor SQL performance using SolarWinds DPA or built-in SQL logs.
Hope this helps.
