Index optimization (was: InterBase's FOR SELECT..SUSPEND equivalent in MS SQL Server

On 22 Nov 2005 16:28:08 -0800, Contraptor@.gmail.com wrote:

> Inserting the indexes did the trick, now the whole process runs in
> under 5 minutes in MS SQL Server.
Which prompts the question: Why is it that the query optimizer doesn't
realize that taking 15 minutes to add an index could save hours of
execution time in extreme cases?Ross Presser <rpresser@.NOSPAMgmail.com.invalid> wrote in
news:dospxcqjmwn4.dlg@.rosspresser.dyndns.org:

> Why is it that the query optimizer doesn't
> realize that taking 15 minutes to add an index could save hours of
> execution time in extreme cases?
My first thought(s):
1. Storage
2. IO/CPU load that slows down rest of the server while processing.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messagingsql