Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 830029 - Last Review: October 27, 2006 - Revision: 1.2
Tempdb Log Exhausts the Available Disk Space When You Try to Update a Collection
When you try to update a large collection, the size of the Templog.ldf file in the \Program Files\Microsoft SQL Server\MSSQL\Data\ folder increases. The tempdb log file increases until the disk space is full.
To work around this problem, move the tempdb transaction log to a disk partition that has more available free space. For more information about how to move a database, see "Attaching and Detaching a Database" in the SQL Server Books Online.
The size of the Templog.ldf file can increase under the following conditions:
- You have a primary site that has many subsites attached. In such a hierarchy, the primary site may have many rule changes to process and replicate to the attached subsites. To process rule changes, the SMS Software Metering Processor
runs a SQL query to write to the tempdb SQL database. The implicit transaction from the SQL query may remain open for a long time. This behavior prevents the truncation of the transaction log.
- The replication of the SMS Software Metering summary data also locks
transactions while returning data is streamed and is written to the summary file.
- A large SMS fan-out hierarchy can decrease site performance. For example, you may experience delays when you generate
advertisements. A large SMS fan-out hierarchy can affect all the SMS component services that replicate data to child
sites. For example, a site with 3000 child sites may spend most of its time replicating objects. As a result, it cannot process
other data.
- User-defined collection queries may use large amounts of tempdb and tempdb log space when the
collection is evaluated. For example, a query that returns many rows per
computer and selects many computers can use large amounts of tempdb and tempdb log space. If the tempdb usage increases and much package or client data is not added to the SMS site database, examine any new collection query rules that were created, if any.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
APPLIES TO
- Microsoft Systems Management Server 2003
| kbsmsmeter kbusage kbperformance kbinterop kbmisctools kbnofix kbbug KB830029 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate