Hi all,

resolved my issue.  Process used to diagnose the fault is described for those who are interested :-

1. Enable traceflag 1204 - from this was able to identify tables,processids,spids involved. ...

Not sure how I would attached the profiler trace, so I've detailed the order of events from the profiler trace

1.  spid:72  Time  2006-08-02 14:46:37.690

DELETE FROM FVFileContents WITH (ROWLOCK) WHERE FileContentsGuid=0xFEDA3D64912A4173AD577F9ABD20C3EB...

What can I do, in this instance.  ?

Hi, I will create an output of the profiler trace for this period with the relavant period.

Apologies All the heading should be Help in analysing this 1204 Deadlock Trace

I agree with Aragorn, from sql properties you can set audit level. It is a built in function, why use anything else.

Pargat

I'll have a look on microsoft site, to see if it is a known problem

Ok, I am getting somewhere. I am creating a trace on the server, logged on as local administrator.

I have worked out that on

c:\Document and Settings\Administrator\Tempa file called prfxxx.tmp (where...

It was not in tempdb as that was moved to a separate disk. Not sure which file on c:. will try looking if program files folder increases, which would...