March 10, 2009 at 10:19 am
Hello,
I have got a SQL Server 2005 SP1 and on this server the tempdb is growing quite big.
When I use the shrinkdatabase option (tasks/shrink/shrink database) it reports me that the database is 6199.06 MB big and that 6197.26 MB is available as free space. When I perform this shrink (or script it and run it afterwards) it says that the schrink was completed successfully, but the size is not reduced.
[font="Courier New"]DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages
2 1 793416 1024 392 392[/font]
When I try to shrink the files separately (tasks/shrink/files) it report to me that the database is only 8 MB big and that 4,75 MB is available as free disk space.
When I do the same for the log file it is reported correctly.
I know that this is corrected when I restart the SQL server, but because this is a production server I am not allowed to do this on a monthly base.
So I would like to be able to correct this while the SQL server is running.
Anyone has the same issue and/or knows how to correct this?
P.S.: installing another SP is not a valid option because this is a validated system.
Kind regards,
Peter
March 10, 2009 at 10:55 am
I would not look at shrinking tempdb. I'd look at increase the size of tempdb so that when it starts it has the space needed to meet the processing requirements of your system. The fact that it has grown while the system is up is proof that it needs to be larger. Shrinking it just causes it to have to grow again when it needs more space, and that can easily impact your systems performance.
March 11, 2009 at 5:15 am
I finally found the solution on the Microsoft site.
It appears that it a know bug and that it is fixed with cumulative build 3152.
Here's the link:
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply