Yeah, unfortunately it's out of my control with the vendor, maybe I can yell at them a bit.

I did change a bunch of heaps over, but I figured as this...

Sorry, yes, ignore the duplicate.

I scripted the table def, then scripted each key. I should have skipped the PK.

8755 rows, 2 megs of data, 1 meg of index.

/****** Object: Table [dbo].[jptsys_isel] Script Date: 01/16/2013 13:35:07 ******/

CREATE TABLE [dbo].[jptsys_isel](

[jptsys_isel_id] [int] NOT NULL,

[assyst_usr_id] [int] NOT NULL,

[isel_name]...

Sorry, for some reason SSMS refuses to sort the time descending.

Date,Source,Severity,Message

01/16/2013 09:10:02,spid32s,Unknown,waiter id=processae84bb88 mode=U requestType=wait

01/16/2013 09:10:02,spid32s,Unknown,waiter-list

01/16/2013 09:10:02,spid32s,Unknown,owner id=process770db88 mode=U

01/16/2013 09:10:02,spid32s,Unknown,owner-list

01/16/2013 09:10:02,spid32s,Unknown,keylock hobtid=72057647025356800 dbid=26 objectname=AX_ASSYST.dbo.jptsys_isel indexname=isel1_dx id=lock3d8f8aa80 mode=U associatedObjectId=72057647025356800

01/16/2013 09:10:02,spid32s,Unknown,waiter...

Yeah, that's what I fear 🙂 As they are all commercial products, there's nothing I can do as a DBA. 🙁

Okay, I was hoping the trace would throw errors for this.

I might have to dig this up

http://www.microsoft.com/en-us/download/details.aspx?id=14845

And make a VM with SQL2000 and run this tool on it.

How many disks are in your array? Is it one big LUN for all disks?

It could be the simple fact that now that you've cleared up 1TB of space at...