CMDB Query Builder, why do the results remain within Columns & Tables?

[TRVLD]

Greetings,

users with cmdb_query_builder role may create QB Queries and Save them, once they do, a new record appears within [qb_saved_query], moreover additional line appears within data collector visible within Columns & Tables: 

Therefore a couple of questions arise:

1. Are these QB Results treated as a new Tables, do they incur new capacity cost for production environments?

2. If user deletes Saved CMDB Query, or admin removes record from [qb_saved_query] the record within Columns & Tables still remains. Same behavior detected on both DS & Tokyo, I didn't built any API that would utilize QB Results, but still what is the purpose for these qb results to remain?

3. With proliferation of QB Querries Columns & Tables gets bulky, how does it affect performance?

Thank you for the advice,

BR,

MJ

[Appli]

Hi, as per KB0954629 - these query results tables are counted as Custom Tables; this has an impact on license fees.

ServiceNow confirmed this is a problem as these result tables should not be counted towards a customer's custom table allotment. When fixed, these will not be counted.

However after deleting a query, its result tables are being deleted as well, just checked in my PDI of Tokyo release.

[Niklas Peterson]

Hi,

Even though they start with u_cmdb... they also extend Query Builder Results (cmdb_qb_result_base). At least in my Tokyo instance.

Which means they should be exempt based on the rule "Customer is entitled to extend each of the below ServiceNow provided tables up to one thousand times".  

cmdb_[*]

https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/custom-table-gu... 

So less than 1000 query builder tables should not be a problem.

Regards,
Niklas

[TRVLD]

My Tokyo PDI, does return following alert each time I try to save a new QB Query within QB interface:

and redirects to something alike:

However, a new Saved Query appears to be saved correctly, and instantly enlisted within Columns & Tales.

What I managed to test, is whether deleting of record from [qb_saved_query] brings the same effect as removal of a Card from QB interface, so far the same effect. Saved query disappears, but the qb_result tables remain.

[Appli]

Hi, please check if you create a CMDB query in a global scope. 

If not, there is indeed some instability.  As per my tests, executing activities below will not delete a resulting table (which extends Query Builder Results):

- change the scope in PDI (I used Tokyo) to any that is not Global. I used Agent Workspace

- go to CMDB Query Builder module

- create CMDB query, Save it and Run it

- error will be shown : 

- delete saved Query

Result: query will be deleted from Query Builder UI, but the corresponding table will stay, till someone will delete it manually.