Announcement

Migration of this forum

Dear users of this forum,

we are pleased to inform you that we will be updating the software behind this forum in the near future.

Existing posts, users and categories will remain untouched.

Important:

  • Each user will need to reset their password.
  • Please select "I forgot my password".
  • Enter the email address you used to register in this forum.
  • You will receive an email with a link to set a new password.
  • Please choose a new (secure) password and confirm the process.

We will keep you informed in the pinned thread.

Kind regards,
Your ReportServer Team


Migration des Forums

Liebe Nutzer dieses Forums,

wir freuen uns, euch mitteilen zu können, dass wir in naher Zukunft die Software hinter diesem Forum aktualisieren werden.

Existierende Beiträge, Nutzer und Kategorien bleiben weiterhin bestehen!

Wichtig:

  • Jeder Nutzer muss sein Passwort neu vergeben.
  • Wählt dazu einfach "Ich habe mein Passwort vergessen".
  • Gebt die E-Mail-Adresse ein, mit der ihr registriert seid.
  • Ihr erhaltet eine E-Mail mit einem Link zur Passwortvergabe.
  • Bitte wählt ein neues (sicheres) Passwort und bestätigt den Vorgang.

Wir halten euch im angepinnten Beitrag auf dem Laufenden!

Mit vielen Grüßen
Euer ReportServer Team

#1 2016-12-13 15:16:27

bpeikes
Member
Registered: 2016-10-29

Huge rs_audit_log_property table

We have a relatively small install of report server, but for some reason, the rs_audit_log_property table has over 4 million records, and is taking several gigs of space on disk. Is there anyway to reduce the size?

Offline

#2 2016-12-18 14:35:13

jalbrecht
Administrator
Registered: 2016-10-21

Re: Huge rs_audit_log_property table

Hi bpeikes,

Check

SELECT E.*, P.KEY_FIELD, P.VALUE
FROM RS_AUDIT_LOG_ENTRY E join RS_AUDIT_LOG_PROPERTY P on E.ENTITY_ID = P.LOG_ENTRY_ID
ORDER BY DATE_FIELD desc

to see relation between RS_AUDIT_LOG Tables ..ENTRY and ..PROPERTY. In General several Property rows match with one ENTRY row. Always deal with both of them. They provide you with useful statistics about your instance.

Whenever you manipulate table content make sure you have a restore option. Only Delete Log Entries when Reportserver is down.

Hope that helps

Jan

Offline

#3 2016-12-19 18:14:21

bpeikes
Member
Registered: 2016-10-29

Re: Huge rs_audit_log_property table

I see the relationship, but how would you recommend trimming this down? Does this table simply keep growing?

Offline

#4 2017-05-25 02:16:26

bpeikes
Member
Registered: 2016-10-29

Re: Huge rs_audit_log_property table

Just wondering if there is a recommendation on how to trim the audit logs. The rs_audit_log_property table is now 9GB. You said that we'd need to trim them, but it's not clear how. For instance, is there a cascade delete between rs_audit_log_property and the rs_audit_log_entry table?

Ideally, there would be a way from the interface to clear the audit log, or at least part of it. I can't imagine why we would have such a ridiculously large audit log. There are not that many changes made to this server.

Offline

#5 2017-05-29 13:18:35

jalbrecht
Administrator
Registered: 2016-10-21

Re: Huge rs_audit_log_property table

Hi bpeikes,

pls. check: https://reportserver.net/en/guides/admi … intenance/

and here:
17.2. Logging
All actions, such as changes to reports or execution of reports are logged in the ReportServer's audit log. The log is split over two database tables. The table RS_AUDIT_LOG_ENTRY contains all logged actions while the table RS_AUDIT_LOG_PROPERTY contains additional information for each action. Note that the tables are not truncated automatically and that on a system with heavy load the tables can thus become very big. It is hence recommended to set up an automatic archiving task. This can be achieved using a ReportServer script, or externally using the native scheduler of your RDBMS.

In RS CE Edition there is no scripting, hence use your RDBMS's Scheduler to empty the tables ...

wbr jan

Offline

Board footer

Powered by FluxBB