Looking for deadlocks

Post Reply
jkj2001
Posts: 142
Joined: Fri Mar 29, 2002 1:39 pm

Looking for deadlocks

Post by jkj2001 »

We've got a table on our NT server (version 3.01.992447526) that appears unresponsive. The indexes are fresh from yesterday morning, but when we try to do things like "select count(A_FIELD)" on the table tsql just sits there.

Granted, it's a table with about a million records, but no large text-- the .tbl file is about 650 MB in size. Maybe 35 fields in the table total.

I thought I'd try my luck, and do a reindex on one of our unique, counter fields (using "create unique index.."), but all that's happened in the last half-hour is a 44 byte .btr file has appeared. No temporary files have been created to indicate the indexing is running along, very atypical.

The box itself has 2 GB of Ram, and according to NT's task manager is barely using any of it. My own PC should look so good. The processor utilization floats from between 1% and 10%, so it's not slammed with other things to do. Also, our other texis tables on this machine run just fine.

I've run monitor -k, to see if that might fix things here, but it doesn't appear to have done so. Could you give a few suggestions as to what might be locking things up, maybe a few ideas to try, places to check, that sort of thing? Thanks a bunch.
jkj2001
Posts: 142
Joined: Fri Mar 29, 2002 1:39 pm

Looking for deadlocks

Post by jkj2001 »

We do have recent indexes on the fields in question-- they just don't seem to be contributing anything.

Also, and I don't know if this triggers any warning signs, when I dropped an index in this table, everything went away except for its .btr file. Ordinarily that will go along with the _T and other associated files, won't it?
Post Reply