Timeout expired. The timeout period elapsed prior to completion of the operation -- dotnet academic

Manoj K
1/3/2004 12:36:07 PM

Environment:-
Framework 1.1
DB: SQL Server 2000 (SQL Provider)
OS: Windows 2000
Language: VB.NET

I'm trying to do mass inserts/updates. Using Transactions.
The table hierarchy contains 3 levels (TL1, TL2, and TL3):
Here is what I'm trying to accomplish:

1) Start Begin Transaction (in desperation, I've tried all
the isolation levels- I was hoping ReadUncommitted would
work!)
2) Do an Insert/Update in table TL1 (this works).
3) Grab the ID from step 2 and do a SELECT on table TL2 to
determine if I need to an UPDATE or INSERT.

Since I'd be inserting 3 rows into table TL2 (for a
particular parent ID with different types), the first
SELECT (on TL2) works and then I'm able to do an INSERT
into TL2. The transaction is still alive. Now, I try to do
a SELECT on table TL2 to see if a record exists for this
type and this is when I get the exception "Timeout
expired. The timeout period elapsed prior to completion
of the operation or the server is not responding."

My guess is that I have a LOCK on the table TL2 (from the
first SELECT), which seems to be causing the problem.

Note:
The INSERTs and UPDATEs are done by executing stored procs.
For the SELECTS, I'm using a different connection (from
the one which the transaction is using) and close it after
the SELECT is executed.

Peter van der Goes
1/3/2004 3:17:17 PM

[quoted text, click to view]
If you don't get any suggestions here, may I suggest the following groups?

microsoft.public.dotnet.framework.adonet
microsoft.public.dotnet.languages.vb
and numerous candidates that begin:
microsoft.public.sqlserver...

All can be found on the Microsoft public news server, msnews.microsoft.com.

--
Peter [MVP Academic]

dotnet academic : Timeout expired. The timeout period elapsed prior to completion of the operation