topic Re: dbo.SubscriptionsHistory table depuration in Report Server

dbo.SubscriptionsHistory table depuration

Anonymous — Wed, 17 Jul 2019 21:48:59 GMT

Hi!

We were looking for metadata information in the ReportServer database to obtain the history, length and status of schedule refresh processes. We discovered the "dbo.SubscriptionsHistory" table. However, there's a weird behavior: in DEV server, the table contains the entire history since installing; in PROD server, the table only contains the last 10 days.

Is there any configuration that we can move (either at instance or database level) to let the table keep more history days?

Regards!

Re: dbo.SubscriptionsHistory table depuration

Anonymous — Thu, 18 Jul 2019 12:31:09 GMT

I think this is controlled via an amdin setting about general execution history retention

Conection to your SSRS Server usings SSMS. I have to use the URL to my server http://ServerName/ReportServerURLPath/ fo this connection and you obviosuly need to be an admin.

Right click and sleect propeties, then I think it's this page

Re: dbo.SubscriptionsHistory table depuration

Anonymous — Thu, 18 Jul 2019 20:44:13 GMT

Hi! Thank you so much for the answer.

I don't have admin access to the production server, but checking the develompent one, that configuration has a 60 days expiration period, but in the table we have information since late 2018.

Is there any other place where this can be configured?

Regards,

Re: dbo.SubscriptionsHistory table depuration

Anonymous — Fri, 19 Jul 2019 14:42:29 GMT

Looking at the code in the ReportServer DB I can see there's a stored procedure called

[dbo].[AddSubscriptionHistoryEntry]

This seems to add entries but then also deletes all entries except the last ten (the ten is hard coded)

Looking at the data on my servers this seems to be what is happening. So I don't understand how you're seeing more than ten entires on your dev systems.

I'm guessing you could amend the stored proc! :smileysurprised:

Re: dbo.SubscriptionsHistory table depuration

Anonymous — Tue, 23 Jul 2019 13:52:09 GMT

Thank you for your answer!

I'll check the stored procedure in dev. However, I doubt the IT team will let us modify a system stored procedure :(.

Regards!