I need to curse on SQL server a bit.

I ran across a query this week that I had to optimize, because the report based on the query was taking too long. I'll admit it was a very ugly query, with a mix of sub queries and joins, against tables with non-existant or wrong headed indexes.

But I've really got some unpleasent things to say about a query optimizers where taking out a WHERE clause that said "tableA.ID = tableA.ID" resulted in a very different and less optimized query.

Jay