August 20, 2012 at 7:55 am
I think that if you don't have your log file backed up it will not shrink.
August 20, 2012 at 8:27 am
You don't need to take a log backup if the db is in simple recovery model -- indeed, you can't: SQL doesn't allow a log backup to occur while the db is in simple mode.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
August 20, 2012 at 8:46 am
is the ReportServerTempDB allways in simple recovery mode?
I'm not using this product. I didn't know that.
Thank's
August 20, 2012 at 8:47 am
It should be, it's a temporary work db, just like tempdb :-).
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
August 20, 2012 at 8:52 am
Ya'll are making the assumption that the problem is ReportServerTempDB. It's entirely possible that 400 GB is the correct size for it and there are databases that are not simple recovery that have transaction log bloat due to a lack of backups. As I said above I've seen small databases with HUGE log files because no one noticed that it wasn't being recovered.
Don't forget the op is not the DBA supporting the server and only knows that a particular drive with database files is full. ReportServerTempDB may be taking up most of the space but it certainly isn't all of it.
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
August 20, 2012 at 9:06 am
Kenneth.Fisher (8/20/2012)
Ya'll are making the assumption that the problem is ReportServerTempDB. It's entirely possible that 400 GB is the correct size for it and there are databases that are not simple recovery that have transaction log bloat due to a lack of backups. As I said above I've seen small databases with HUGE log files because no one noticed that it wasn't being recovered.Don't forget the op is not the DBA supporting the server and only knows that a particular drive with database files is full. ReportServerTempDB may be taking up most of the space but it certainly isn't all of it.
It's not an "assumption", it was stated in the original question.
Note G:\ is 750Gig
Looking at the log files, the on for database ReportServerTempDB is over 400Gig in size.
If allowed, he could also try stopping and starting Reporting Services, which should reduce the temp log. Even if it doesn't, it would be safe to shrink the log file at that point, so have the command ready to run immediately after the recycle of RS.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
August 20, 2012 at 9:39 am
It's not an "assumption", it was stated in the original question.
Note G:\ is 750Gig
Looking at the log files, the on for database ReportServerTempDB is over 400Gig in size.
If allowed, he could also try stopping and starting Reporting Services, which should reduce the temp log. Even if it doesn't, it would be safe to shrink the log file at that point, so have the command ready to run immediately after the recycle of RS.[/quote]
I'm not saying that it's not a logical assumption, just that it is an assumption. There is an additional 350GB on the drive. It's entirely possible the ReportServerTempDB is supposed to be 400GB and the remaining logs are supposed to be 200GB leaving 150GB free. Some big import may have caused one of the other logs on the drive to have bloated up enough to fill the drive. Or something similar.
Of course it's also possible, even likely, that someone ran a report that caused the ReportServerTempDB to grow and it can be safely shrunk. We just don't really know at this point.
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
Viewing 7 posts - 16 through 22 (of 22 total)
You must be logged in to reply to this topic. Login to reply