Read following KBs.

http://support.microsoft.com/default.aspx?scid=kb;en-us;233161

http://support.microsoft.com/default.aspx?scid=kb;en-us;241643

Can you check whether MSDTC server is started?

quote:

---

I think you are correct that it is a bug in SQL Server. I recreated the final search table in MS Access...

Schedule two backup jobs to run at different time to different locations.

Are you running SQL Server 7.0 and service pack is below sp3? If it is, Read KB article at http://support.microsoft.com/default.aspx?scid=kb;en-us;254253. It was a SQL Server bug.

Have you tried to use "CHECK constraint"?

Try to stop SQL Mail from SQL Server support service. You also may have to stop SQL Server Agent service.

I would suggest you to look into the execution plans on both query. They might be different.

Check "Target Server Memory (KB)" and "Total Server Memory (KB)" in system table sysperfinfo. ...

Detach the database, move the transaction log file to new drive and attach database back. See BOL sp_detach_db and sp_attach_db for details.

Any other applications run in this server too? If they are, check which applications are the cause of paging.

When you added a new node to SQL Server cluster, the SQL Server binaries are copied from installation CD onto the new node.

Fail over to the new node, install...

I would suggest you run dbcc with 'REPAIR_ALLOW_DATA_LOSS' to this table after you move everything to new table and before drop it. The result may be interesting.

Have you tried option 'REPAIR_ALLOW_DATA_LOSS'? You may have to BCP data out, drop table, recreate it, BCP data in and recreate the PK and indexes as work around.

Can you check the version of sqlservr.exe in both nodes to see whether they are same?