Posted by Erland Sommarskog on 08/26/06 20:50

(msmith@crypticedge.net) writes:
> I have a database in houston, lets call it RED. Specific tables from
> database RED are copied to database BLUE. Database BLUE is then backed
> up, ftp'd to memphis and restored. In memphis there is a single table
> in this database that will not open in enterprise manager when you
> choose to open all rows you get a generic ODBC timeout error no numbers
> just simply "TIMEOUT".

How many rows are there in this table? What happens if you run a
SELECT * on this table in Query Analyzer?

My guess would be that there is a blocking issue. You can examine this
by starting the query and while waiting for the results, run sp_who or
sp_who from a query window. Keep an eye on the Blk column. If this
column has a non-zero value, it means that the spid in the Blk is
blocking the spid on this row. (spid = server process.)

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: Merging two tables with selection
• Prev in forum: Re: Primary key generating
• Thread view: Re: Table Query Timeout Problem very specific

[Reply to this message]