Emptying reportservertempdb

I have a reportservertempdb database that has suddenly grown to 16Gb and has
stayed that way for a few days. How do I clear what might be cached in there
and/or get this database to shrink back down to a reasonable size?John,
We are experiencing exactly the same problem as you described: the
ReportServerTempDB suddenly grow to over 10GB and stay that large.
We recently run large number of reports, more than 5,000 pages, with
images merged in using URL on every page. At first, the transaction
log grow rapidly to over 15GB. We then turned off the caching,
controled the size of the transaction log, and scheduled backup of the
transaction log every hour. Now the size of the tranaction log is
under control, but there is a table named CHUNKDATA in
ReportServerTempDB which stayed to be large (over 11GB). I wonder if
it is save to truncate the CHUNKDATA table. And how to correctly
control the overall size of this database.
If you or anybody found or heard of any solutions to this problem,
please share them with me.
Thanks in advance!
Tommy|||I'm thinking since nothing in that database is important I'm going to drop
and recreate it from a script. I too turned off all caching but it didn't
help.
"Tommy" wrote:
> John,
> We are experiencing exactly the same problem as you described: the
> ReportServerTempDB suddenly grow to over 10GB and stay that large.
> We recently run large number of reports, more than 5,000 pages, with
> images merged in using URL on every page. At first, the transaction
> log grow rapidly to over 15GB. We then turned off the caching,
> controled the size of the transaction log, and scheduled backup of the
> transaction log every hour. Now the size of the tranaction log is
> under control, but there is a table named CHUNKDATA in
> ReportServerTempDB which stayed to be large (over 11GB). I wonder if
> it is save to truncate the CHUNKDATA table. And how to correctly
> control the overall size of this database.
> If you or anybody found or heard of any solutions to this problem,
> please share them with me.
> Thanks in advance!
> Tommy
>|||need to delete snapshots that are in history.
John wrote:
>I'm thinking since nothing in that database is important I'm going to drop
>and recreate it from a script. I too turned off all caching but it didn't
>help.
>"Tommy" wrote:
>> John,
>> We are experiencing exactly the same problem as you described: the
>[quoted text clipped - 16 lines]
>> Tommy
--
Gene Hunter
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200508/1