Error writing binary data

Dear all,
we run a SQL Server 2000 SE 8.00.534 SP2 on a 2 CPU server.
We have three similar databases, which all contain a table to store binaries
as base64-Text.
From time to time we face a problem writing in one of this tables. The
requests get a timeout.
Its always the same table in the same database. The other tables never
caused any problem.
Reading access ist no problem, but writing doesn't work.
We can fix the problem by copying the data in a new table an rename them
that the new table replaces the old one. Sometimes the problem ist solved
when we add a new index (doesn't matter which column) and save the table.
You can't see any difference between the the table in the relevant database
and the other ones.
Even a restart of the whole machine doesn't solve the problem, so that locks
shouldn't be the cause.
Any tips?
Greeting from Germany
Matthias MerzHi
There are a significant number of changes between the version you are
running and the current version (2187) so you may want to review the KB
article to see if there is anything that may have fixed this
http://www.aspfaq.com/sql2000builds.asp
If you are getting any error messages in the SQL Server log or the Windows
Event log will help.
You don't say if dropping all indexes helps!!!
John
"Matthias Merz" wrote:

> Dear all,
> we run a SQL Server 2000 SE 8.00.534 SP2 on a 2 CPU server.
> We have three similar databases, which all contain a table to store binari
es
> as base64-Text.
> From time to time we face a problem writing in one of this tables. The
> requests get a timeout.
> Its always the same table in the same database. The other tables never
> caused any problem.
> Reading access ist no problem, but writing doesn't work.
> We can fix the problem by copying the data in a new table an rename them
> that the new table replaces the old one. Sometimes the problem ist solved
> when we add a new index (doesn't matter which column) and save the table.
> You can't see any difference between the the table in the relevant databas
e
> and the other ones.
> Even a restart of the whole machine doesn't solve the problem, so that loc
ks
> shouldn't be the cause.
> Any tips?
> Greeting from Germany
> Matthias Merz
>
>