Posted by CK on 10/01/39 11:32

It's not blocked. After some testings, I realised the problem was caused by
insufficient free harddisk space for the transaction log file. It worked
fine after I created another log file in a drive with plenty of space.
Nevertheless, I was surprised that SQL Server didn't give me any warning
message about this.


"Hugo Kornelis" <hugo@pe_NO_rFact.in_SPAM_fo> wrote in message
news:gc2vn1tfeb652jnj32vhl2li4qjq0l05fm@4ax.com...
> On Sun, 20 Nov 2005 00:17:11 +1100, CK wrote:
>
>>Thanks for letting me know about this command. Otherwise I would have
>>waited
>>forever without realising the process is in the state of "sleeping".
>
> Hi CK,
>
> But is it also blocked?
>
> (Check the column BlkBy)
>
> Best, Hugo
> --
>
> (Remove _NO_ and _SPAM_ to get my e-mail address)

[Back to original message]