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

transaction log eats up all the space and growing until sql is stopped Expand / Collapse
Author
Message
Posted Friday, November 22, 2013 2:47 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, February 27, 2014 9:04 PM
Points: 46, Visits: 113
i've had to restart it again, because its run off space again. i will have an update soon..

Post #1516693
Posted Friday, November 22, 2013 3:43 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 1:06 PM
Points: 2,829, Visits: 8,479
USE Database_WithBigLog

DBCC OPENTRAN



Post #1516711
Posted Tuesday, November 26, 2013 7:42 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, February 27, 2014 9:04 PM
Points: 46, Visits: 113
Thanks, That returned me the following results. From the start time this seems like this process's been running for over 3 days.

Oldest active transaction:
SPID (server process ID): 58
UID (user ID) : -1
Name : user_transaction
LSN : (473273:176905:59)
Start time : Nov 24 2013 11:31:44:010PM
SID : 0xb6e2b7cea93af54eb49780a9ff6d2b0b
Post #1517874
Posted Tuesday, November 26, 2013 7:53 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, February 27, 2014 9:04 PM
Points: 46, Visits: 113
Adding on to my earlier message:

Noticed the following process triggered via SQL agent running since then; seems to be a DELETE command:-


purge_stat1_proc


Post #1517877
Posted Tuesday, November 26, 2013 9:58 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:28 PM
Points: 43,028, Visits: 36,193
mJai (11/26/2013)
Thanks, That returned me the following results. From the start time this seems like this process's been running for over 3 days.

Oldest active transaction:
SPID (server process ID): 58
UID (user ID) : -1
Name : user_transaction
LSN : (473273:176905:59)
Start time : Nov 24 2013 11:31:44:010PM
SID : 0xb6e2b7cea93af54eb49780a9ff6d2b0b


Yup, that looks like a suspect.

Query sys.dm_exec_sessions and sys.dm_exec_connections and see where session_id 58 is coming from, which login, what machine, what application. USe the most_recent_sql_handle column of sys.dm_exec_connections along with the sys.dm_exec_sql_text function to see the last thing it ran. That combined should give you a good idea of where this open transaction is coming from.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1517894
Posted Tuesday, November 26, 2013 10:32 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, February 27, 2014 9:04 PM
Points: 46, Visits: 113
Yes' Got the culprit, you're right.

Its the vmware stored procedure. Ah!

Thanks..
Post #1517902
Posted Wednesday, November 27, 2013 12:02 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:28 PM
Points: 43,028, Visits: 36,193
If it's leaving a transaction open, I suspect the procedure's failing somewhere or has something else wrong.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1517921
Posted Wednesday, November 27, 2013 6:19 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, February 27, 2014 9:04 PM
Points: 46, Visits: 113
Yes, they, the vendor have released couple of patches/workarounds to address those issues. Thanks.
Post #1518241
Posted Thursday, December 12, 2013 5:00 PM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: 2 days ago @ 11:28 AM
Points: 553, Visits: 1,618
Be careful with log drive space when upgrading VCenter. Our adventure last week was a VCenter upgrade that kept growing the VIManage.ldf file until it filled the drive. My solution was to set the Max size of the log file to the drive size -10 GB and temporily add a 2nd Log file to a temporary drive. The total size of both log files eventually reached 130 GB. The correct size for the log file in our VMCenter environment for normal operations seems to be about 30 GB.
Post #1522522
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse