You are not logged in.
Pages: 1
We're looking to improve the performance of ReportServer and we were wondering if its possible to disable the 'auditing' actions recorded in the operational database ?
Thanks !
Offline
Hi dee,
welcome to the ReportServer forum. You should be able to shutdown the audit logging by executing the following script:
import net.datenwerke.rs.utils.eventlogger.EventLoggerService
def service = GLOBALS.getInstance(EventLoggerService.class)
service.shutdownWatchdog()
service.shutdown()
Out of curiosity. Do you have any indication that the audit logging affects the performance of your database?
Cheers
-Arno
Offline
Thanks Arno !
When you say execute the script - in what way ? sorry if I'm asking something which is obvious.
Now that we know how to shut it down we'll be able to benchmark it.
We'll update on the results if thats something that could assist anyone.
Thanks
Last edited by dee (2015-03-24 17:12:24)
Offline
Hey dee,
I am definitely interested in any benchmarks that you are making.
Cheers
-Arno
Offline
When you say execute the script - in what way ? sorry if I'm asking something which is obvious.
Offline
ReportServer scripts go in the internal file server somewhere below the bin directory. You can execute a script from the terminal (CTRL+ALT+T opens the terminal). Assuming your script is in /bin/tmp/disableauditlog.groovy you can execute the script by running the commands
cd /fileserver/bin/tmp
exec disableauditlog.groovy
For further information have a look at the admin and scripting guides http://www.reportserver.net/en/services/.
Cheers
-Arno
Offline
Hi,
instead of completely shutdown the audit, how is possible to reduce the log's level?
Thanks,
Alex
Offline
Hi Alex,
ReportServer currently does not distinguish between different log levels.
Cheers
-Arno
Offline
Pages: 1