DROP DB 'HISDBHERE'

quote:

---

Originally posted by jsmith8858

quote:

---

Originally posted by tkizer

quote:

---

Originally posted by dinakar

Theoretically it should be better since using functions on column names especially in WHERE clauses can force table scans..

---

I don't believe that's the case in his situation since the column is isolated on one side of the predicate:

WHERE ColumnName = SomeFunction(...)

Perhaps this is what you are referring to:

WHERE SomeFunction(ColumnName, ...) = SomeValue

Tara Kizer
http://weblogs.sqlteam.com/tarad/

---

Actually, that is not correct, the column is not isolated on one side ...
The column is referenced on BOTH sides.

This is actually the situation:

WHERE ColumnName = SomeFunction(... ColumnName ... )


- Jeff
http://weblogs.sqlteam.com/JeffS

---