Viewing 8 posts - 1 through 8 (of 8 total)
Oldest active transaction:
SPID (server process ID): 9s
UID (user ID) : -1
Name ...
February 11, 2011 at 10:47 am
actually i did stopped and restart the sql server agent
than i shrink the file
I think this bought down the log file from 122 gigs to 24 gigs
But i think...
February 11, 2011 at 10:13 am
yes blocking session id is 0
restart sql is an option but not right now as it is production but let me check
you want me to stop and start the sql...
February 11, 2011 at 9:25 am
I queried sys.dmexec_requests and see 3 session waiting since 44 hours
session_idrequest_idstart_timestatuscommandsql_handlestatement_start_offsetstatement_end_offsetplan_handledatabase_iduser_idconnection_idblocking_session_idwait_typewait_timelast_wait_typewait_resourceopen_transaction_count
2402011-02-09 10:20:07.653backgroundBRKR TASKNULLNULLNULLNULL11NULL0BROKER_TRANSMITTER178348044BROKER_TRANSMITTER0
2502011-02-09 10:20:07.653backgroundBRKR TASKNULLNULLNULLNULL11NULL0BROKER_TRANSMITTER178348044BROKER_TRANSMITTER0
902011-02-09 10:20:07.653backgroundSIGNAL HANDLERNULLNULLNULLNULL11NULL0KSOURCE_WAKEUP174755473KSOURCE_WAKEUP1
February 11, 2011 at 8:56 am
how do i check what process is running this ?
Can i kill it and shrink the log file
when i check in the replication monitor the log reader and distributer seems...
February 11, 2011 at 8:06 am
Checked the job under publisher and subscriber both the server the log reader job is running
February 11, 2011 at 7:57 am
Also i tried stopping the replication and shrinking it that did not work too
February 11, 2011 at 7:35 am
I am running transaction log replication
February 11, 2011 at 7:34 am
Viewing 8 posts - 1 through 8 (of 8 total)