Hi. I have a SQL Server running on:
DELL PowerEdge 2950
4 GB Memory
1 Processors with 4 Cores
Windows 2003 Standard - 32 bit
...and one 20 GB database. Normally, everything runs very quickly. In
certain edge-cases such as: user requests 14 month report resulting in query
joining 400,000 rows
The Database Engine Tuning Advisor only gets you so far and some of
the recommendations it generates are bad recommendations. For example,
it might suggest redundant overlapping indexes. It currently takes a
human to properly set up indexes.
Your best bet is to find the bottleneck and try to
Mike had a lot of good comments. How dynamic is your data? Is it constantly
being updated? If so, do you need real-time query results?
You need to balance the creation of indexes (as many as possible on a
relatively static server) with the fact that indexes can slow down
As an adjunct to the advice you've already received (which is
excellent I might add), I always recommend looking at the business use
cases for reporting. Are these reports ad hoc reports or are they
known reports that you can schedule ahead of time, execute during off
hours, then save the results
4 matches
Mail list logo
