Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Problems changing SQL data source for custom table in reports

Problems changing SQL data source for custom table in reports

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 969 Votes: 0 Revisions: 8

Issue:

Changing the SQL data source for a custom table in reports resulted in an error message, even though the SQL queries returned the same result.
The message:
"Datasource 1" is not compatible with the resource configuration. Go to {0} to see 
where the problem is.
was displayed.

Cause:

In the initial SQL data source, a field was created using CPULoad.AvgLoad.
In the replacement this was AVG(CPULoad.AvgLoad).

CPULoad.AvgLoad has a datatype of Int16.
The AVG function converts to Int32.

Therefore, the source for the replacement was considered incompatible.
This can also occur with MAX, SUM and other aggregation types.

Workaround:

If this problem occurs:
  1. Determine which columns are causing the incompatibility. This will be where the SQL source code has added or removed an aggregation function such as AVG, SUM or MAX.
  2. Remove the incompatible columns from the Custom Table.
  3. Add the replacement source code again.
Last modified

Tags

Classifications

Public