• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1754
  • Last Modified:

Seeing negative available free space in the Shrink file Task for transaction logs.

We are Seeing negative available free space in the Shrink file Task for transaction logs.
Has anyone ever seen this before?
Our MS SQL Server 2005 DB is running in Simple mode.
This is occuring repeatedly, can someone shed some light on this issue.
Running version: SQL 2005 9.00.4035.00 SP3

More information to come.
   We are Seeing negative available free space in the Shrink file Task for transaction logs.
0
topa101
Asked:
topa101
1 Solution
 
Kevin CrossChief Technology OfficerCommented:
Hi.

Try updating usage information: http://msdn.microsoft.com/en-us/library/ms188414(v=SQL.90).aspx
DBCC UPDATEUSAGE

Open in new window


I have not experienced this, but my databases were freshly created in SQL 2005.  It is likely your databases were upgraded and per MSDN that is a known potential issue.

Hope that helps!

Kevin
0
 
dba2dbaCommented:
Please Run DBCC UPDATEUSAGE or sp_spaceused with @updateusage = TRUE to fix this inaccuracy.

Thanks

Ref.: http://www.bigresource.com/Tracker/Track-ms_sql-BSx6H5Um/
0
 
topa101Author Commented:
These counts are going megative fairly regularly, and the DB was never an upgrade from a lower version.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
Kevin CrossChief Technology OfficerCommented:
Okay.  Did the DBCC UPDATEUSAGE correct the problem or not?  You may need to look at the transactional log needs of the database and determine if you are better suited in full mode doing transaction log backups frequently.  It is not a good sign to have to do SHRINKFILE often.  It is usual an indication of some other issue.  I have one database I have to do that with and it is because it is a 3rd party tool that they do a bunch of deletes from a table with close to a million rows of data versus using truncate to wipe the table whenever it needs to rebuild the data.
0
 
Anthony PerkinsCommented:
>>You may need to look at the transactional log needs of the database and determine if you are better suited in full mode doing transaction log backups frequently.  <<
The author's "MS SQL Server 2005 DB is running in Simple mode", but you are right using DBCC SHRINKFILE is a very bad idea and the only thing worse is scheduling it.
0
 
topa101Author Commented:
There seems to be more to this issue, i will investigate closer and repost with more detail.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now