"Timeout expired"

In a legacy project on the production server, we have a database which
generated the following error when executing a report (written in ASP).
Microsoft OLE DB Provider for ODBC Drivers error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
I then created a SQL dump of this database and exported the tables to Access
MDB file.
Using another test server, I re-created the entire database using the SQL
dump file and imported the data using Access MDB file. Next, I copied the
entire ASP source tree over to this test server.
Lo and behold, when I ran the same report program, it ran successfully!
Could someone tell me why the legacy project running on the production
server caused this timeout error, while the exact same program running on a
test server runs without problem?
Could it be an indexing issue?
Thanks.Ed,
"Ed" <eddiemarino@.hotmail.com> wrote in message
news:OjVEPFt6DHA.2392@.TK2MSFTNGP11.phx.gbl...

quote:

---

> Could someone tell me why the legacy project running on the production
> server caused this timeout error, while the exact same program running on

---

a

quote:

---

> test server runs without problem?
> Could it be an indexing issue?

---

Yes, it could be indexing.
It could also be locks, server load, etc.
Dev servers tend to be less busy than production machines, and what works
well in the sandbox might not be so hot when the server's really up against
it.
If you've not done so, start by having ASP developers set a custom timeout
value to something other than the default.
(Assuming, of course, identical schema between test and production <g> )
James Hokes