Re: Timeout with Where statement
From: Val Mazur (group51a_at_hotmail.com)
Date: 05/22/04
- Next message: Val Mazur: "Re: ADO call to user defined function"
- Previous message: Chaoxiang: "Can I use the ADO to get the server' time"
- In reply to: Frank Petrucci: "Re: Timeout with Where statement"
- Next in thread: Frank Petrucci: "Re: Timeout with Where statement"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 21 May 2004 22:24:14 -0400
Hi
Try to check query execution plant to see where your query spends most of
the time
-- Val Mazur Microsoft MVP "Frank Petrucci" <fpetrucci007@yahoo.com> wrote in message news:2E38353C-BAAA-4D47-B4D5-6B96D1061FF3@microsoft.com... >I tried creating indexes using the fields in the query: > SELECT TOP 10 * > FROM GRS.IDX_DOC INNER JOIN > GRS.IDX_DOC_PROP ON GRS.IDX_DOC.DOC_ID = > GRS.IDX_DOC_PROP.DOC_ID INNER JOIN > GRS.IDX_PROP ON GRS.IDX_DOC_PROP.PROP_ID = > GRS.IDX_PROP.PROP_ID > WHERE (GRS.IDX_DOC.RECORDED_DATE > '1/2/2003') AND > (GRS.IDX_DOC.RECORDED_DATE < '1/16/2004') > > but I still get a timeout running under enterprise manager. I did not > create clustered indexes. Do you think I need to add more fields to the > index to make it run faster?
- Next message: Val Mazur: "Re: ADO call to user defined function"
- Previous message: Chaoxiang: "Can I use the ADO to get the server' time"
- In reply to: Frank Petrucci: "Re: Timeout with Where statement"
- Next in thread: Frank Petrucci: "Re: Timeout with Where statement"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|