How to enable the probe "Log SQL user" cache in V4.0

4.0
How to enable the probe "Log SQL user" cache in V4.0
0
Tags: #<Tag:0x00007fcf1ac88a98>

#1

how to enable the probe “Log SQL user” cache in V4.0 !?


(David AZOULAY) #2

I don’t understand what you mean by “Log SQL user” cache
What is your requirement?


#3

I mean by “Log SQl user” to enable cache of SQL, and to know the query of SQL.


(David AZOULAY) #4

It is the term “cache” that I don’t understand in this context…

Are you just speaking of logging SQL requests ?


#5

Yeh


#6

I’m speaking for activate probes:

  • Move the “LOG_SQL_USER” system parameter to “yes” and clear all caches
  • Access times will be longer and the logs are large, so you have to activate this probe only in design / test.
  • Server logs will contain all user queries
  • Move “LOG_SQL_USER” parameter to “no” and clear the cache to stop the tracing.

(David AZOULAY) #7

Ok it seems that you managed to activate these log traces…

Keep in mind that this must be temporary as this is highly resources-consuming

Note that you can review the server logs directly in the browser’s console provided the websockets works for you (sometimes it is not the case thru some restrictive entreprise proxies), the legacy log viewer is only for those having trouble with websockets…


#8

I didn’t quite understand it


(David AZOULAY) #9

That is why I asked you initially what was your requirement.

For instance do you want to review these traces for training purposes (to understand what is the engine is actually doing), or for a specific issue investigation, or …

I ask because in general reviewing the SQL statement generated by the platform is not very useful.


#10

For training, because I just do my first step in Simplicité


(David AZOULAY) #11

I discussed this point with the team, the training should not describe this rather unusual and confusing feature… We will remove it from the training.