Summary:  We have been getting a reoccuring time out error when running a
single one line insert into a table. The timeout occurs until we run select *
from the table. This is for SQL Server 2000.  
___________________________

We have been getting a reoccuring time out error on an insert statement.  
The insert inserts a single row into a table.  We will call this table
'table1'  Once the timeout error starts occuring any insert  into the table
will timeout. This is regardless if it is the code from inside the asp.net
app,  or if it an insert into the table is run from inside table analyzer.  
The timeout keeps occuring until from inside query analyzer we run the query
'select * from table1'.  This then fixes the issue and all inserts start
working again for a few months. After a few months the timeouts start
occuring again, until we rerun that select statement.

The only operation that we do to table1 is inserting a single row, and
reads. NO explicit locks or transactions are applied to the table.  But it
seems that either some sort of deadlock keeps happening, or an index
corruption is occuring.

Can anyone tell me why this error keeps occuring, and what can we do to
esure that this issue does not occur again? Is this a lock issue, or an index
issue? Is it some problem with the code, or a bug in SQL Server?

I have below the code that was used inside of the stored procedure, (note  
the column,table and variable names changed are changed from the original).
This procedure is the only place that any update operation is done to
'table1' at all. Anything else is merely reads.

CREATE PROCEDURE dbo.DoInsert
AS
declare @gid as varchar(50)
declare @id as integer
set @gid=newID()
set nocount on
 Insert into table1(gid, startTime) values (@gid, getdate())
 set @id=scope_identity() --as identityInsert
set nocount off
  select @gid as 'gid', @id as 'id'