Just found it!  The problem was with the smalldatetime column linking to another table having datetime type.

So if you change this:

declare @b-2 table

(

 dt   smalldatetime,

 block_spid   smallint,

 who_spid  smallint

)

To...

Unfortunately it did not work.  If you can't use a cursor to perform the task, you can not use this SP as well.

Yes, but this solution also has it's limitations, like not being able to send job alerts and @query parameter not being supported.

Thanks, but I was looking specifically for document about using Outlook 2003 with SQL Server 2000, like this one:

http://support.microsoft.com/default.aspx/kb/263556

But this one only tells about Outlook 2000 & 2002 configurations...

Yes, the hardware is exactly the same, all I change is OS (Win 2003 Server 32/64bit) and SQL Server (MS SQL 2005 32/64bit).

Yes, this is an Intel box: Two way Dell PowerEdge 1850 8GB of RAM,  3200MHz Xeon CPUs.

I am not sure, what is PSS?  What is their web address?

Already did so, the error persists.  I am wondering if there are any crack/hack type tools to correct allocation errors?

I am using it, but sometimes I need more flexibility than drill through functionality can offer.  If there no standard aproach for running such queries, is there any OLAP client...

No triggers on both tables.  The actual updates are:

update  SORDER set occur=occur where sorder = 12345 -- fast table

&

update STOCK_INVOICE set occur = occur where stock_invoice = 345...

There are six FK that reference that PK (a dozen on a "fast" table), but I am not updating th PK, but using it as search criteria:

update table...

The "fast" table has three times more records, but it does not much matter, because I use a clustered index on PK.  The "fast" also has more user activity on it. ...

Already did this - the same error.

Hewlett Packard support advised to replace 3-port internal FC-hubs with switches as well as to upgrade Secure Path 4c with sp1 and to upgrade HBA firmware.  The main focus of...

Which of the two problems do you mean?  The database restore problem, with disabled array accelerator?  I solved it by removing the named-pipe alias, needed to install MS SQL 2000...