Testing if SQL PurgeForTable went wrong

Question

Question

Mathew Lambert · Jan 12, 2021

Does anybody know if there is an easy way to know if the execution of the command $System.SQL.PurgeForTable went well/wrong?

The documentation describes that a string is returned, but in fact there is a nice Quit "" in the code.

Maybe inside PurgeForTable^%apiSQL there is any process variable set when it goes well/wrong?

Thank you very much!

Discussion (5)0

Log in or sign up to continue

Jose-Tomas Salvador · Jan 14, 2021

Hi Mathew,

that method doesn't return any info neither in case of error nor success... as you said, it always return "".

The option that Anderson mentions is a valid one to double-check that everything went well.

0 0

score 0 · Answer 1 · 2021-01-12T08:27:05-05:00

Eduard Lebedyuk · Jan 12, 2021

Only %objlasterror I guess.

0 0

score 0 · Answer 2 · 2021-01-12T11:42:39-05:00

Try use:

##class(%Library.SQLCatalog).GetCachedQueryTableCount("table_name")

This command will return the number of Cached Queries.

So, you can check if all Cached Queries have been purged.

score 0 · Answer 3 · 2021-01-14T04:43:19-05:00

The issue with this option is that on a productive environment, inmediately after purguing the queries, I've got new queries.

score 0 · Answer 4 · 2021-01-14T04:44:19-05:00

Until now in caché we where checking $ZERROR, but as InterSystems is descouraging the use of that variable, I don't know how to surely test this command.