I would look at the query plan first to understand where the problem is.
Then, I would start rebuilding, dropping or creating indexes. I would
bet that the query is not using the index that you think it is
(resulting in a table scan). Or, it may be doing index scans instead of
seeks.


Eric Levinson wrote:
> Try dropping and recreating the indexes.
>
> Eric
>
>
> -----Original Message-----
> From: Noble Mudenha
> [mailto:mssqldba-ezmlmshield-x70273157.[Email address protected]
> Sent: Friday, January 27, 2006 1:08 AM
> To: LazyDBA Discussion
> Subject: Another Performance Issue
>
> Hi guys, suppose I had a transactions table that was taking a LONG time
> to retrieve data from, especially when filtered. It is indexed on all
> columns where criteria to filter is specified. I reindexed (DBCC
> REINDEX) the table, and now it runs slower than before, fillfactor was
> left unchanged. What went wrong, if anything, and what can I do to make
> it faster?
>
>
>
>
>
> ---------------------------------------------------------------------
> TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Website :
> http://www.LazyDBA.com To unsubscribe:
> http://www.lazydba.com/unsubscribe.html
>
>
>
> ---------------------------------------------------------------------
> TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
> Website : http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>
>
> .
>
>

MS Sql Server LazyDBA home page