Timeout Expired

Hello all.

I have a table in SQL Server 2000 with 3.5 million rows in it, approximately
20 columns. I am querying this table via ODBC using the microsoft driver.
Certain
queries fail and return a 'Timeout Expired' message. I have a non-unique index
on the column I am referencing in my WHERE clause. I have determined that
the query takes approximately 1.5 minutes to complete when run through Query
Analyzer and returns 21,000 rows.

Is there a way to improve the efficiency of this index ? Is there a way to
bump
up the timeout period on the server or on the ODBC connection ?

Any help would be appreciated,
Thanks
.

Relevant Pages

  • Re: [PHP] ODBC and long text fields
    ... We've a PHP app that uses ODBC to talk to a MS SQL server. ... The internal code for a query is ...
    (php.general)
  • RE: Timeout Expired
    ... > I have a table in SQL Server 2000 with 3.5 million rows in it, ... I have a non-unique index ... > the query takes approximately 1.5 minutes to complete when run through Query ... > up the timeout period on the server or on the ODBC connection? ...
    (microsoft.public.sqlserver.odbc)
  • RE: Timeout Expired
    ... Try creating the query you are running via ODBC as a stored procedure in the ... This will allow SQL Server to create and store an optimized execution ...
    (microsoft.public.sqlserver.odbc)
  • Re: Query multiple dbs
    ... If you can configure a conection of ODBC to Oracle or MySql, ... we can query Informix from SQL server with the following format: ... Using this format we can make join between tables of SQL Server and Informix. ...
    (microsoft.public.data.ado)
  • Re: SQLGetData performance
    ... V> I need an ODBC-expert opinion regarding SQLGetData. ... V> I have a win32 application that connects to SQL Server through ODBC. ... V> A query that used a particular view took a few minutes to load the ...
    (microsoft.public.data.odbc)
Loading