nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Updating Custom Properties Directly in SQL

byrona

My understanding is that it is safe to update Custom Properties (Node, Volume & Interface) directly through SQL, is this accurate?

Find more posts tagged with

Accepted answers

sean.martinez

Adding information into the Custom Properties columns should not be an issue. Adding new columns to the Tables would cause issues.

All comments

adeimel

I hope so I do it all the time in APM to be able to use custom properties within the dynamic queries...

njoylif

ditto. I think the only time you have to worry is if you have something auto populating the custom property.

sean.martinez

Adding information into the Custom Properties columns should not be an issue. Adding new columns to the Tables would cause issues.

byrona

Adding information into the Custom Properties columns should not be an issue. Adding new columns to the Tables would cause issues.

Thanks Sean!

This is what I thought but figured better to play it safe and verify first.

cgregors

Can you expand on this a bit more please:

"Adding new columns to the Tables would cause issues"

tomas.mrkvicka

Custom properties are represented by columns in given table and also by metadata stored in Information Service. If you add your own column we will have no information about them. It can later caused some issues (e.g. during upgrade) etc.

cgregors

What about doing the following:

create a table and call it "MyAPMTemplateCustomProperties"

then write alerts / reports in sql referencing the extra table for my custom properties.

This could then be extended to :

MyGroupsCustomProperties
MyAPMComponentCustomProperties
...

I have already done something similar by adding an export from a CMDB as a separate table and then using writing sql to generate a report that shows the difference between the two tables.

Chris

tomas.mrkvicka

It sounds reasonably. Of course Orion doesn't know anything about your tables so if you add any new Orion entity (let's say Group) there will be no corresponding record in your table etc.

But if you write your SQL queries carefully there should be no problem.

krishnamishra0786

Hi,

i would like use same query to update node's custom property, could you please help me to text a query, and one more thing same query i can use as a batch file so same could be auto.

thanks