Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Row Level Versioning Expand / Collapse
Author
Message
Posted Thursday, April 22, 2010 6:55 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, July 18, 2014 8:05 AM
Points: 45, Visits: 342
Hi Paul, thanks for the reply.

Answering to your questions, the transaction log of tempdb is set on a different physical device as the tempdb data and both are set to autogrow. Only the tempdb transaction log disk filled all the available space. I am not sure what is really happening and I'm not comfortable in adding more space to the disk without knowing what's going on. I'm already monitoring through perfmon all the version stored in tempdb too.

What might be your suggestion to this case? If it's a long running transaction that is causing this issue, what's the best approach to solve this?

Thanks
Post #908555
Posted Thursday, April 22, 2010 7:14 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 10:42 AM
Points: 11,192, Visits: 11,089
Managing Long-Running Transactions



Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #908578
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse