I'm having a hard time phrasing this question in such a way that doesn't turn up results for persisted, indexed computed columns.
My question is, if I have a table such as:
CREATE TABLE Customers (
ID int,
Name nvarchar(50),
Balance money,
HasBalance AS CONVERT(bit, CASE WHEN Balance > 0 THEN 1 ELSE 0 END)
)
Assuming that there's an index on Balance, would the SQL query processor efficiently process a query such as:
SELECT ID, Name, Balance
FROM Customers
WHERE HasBalance = 1
Will it essentially "inline" the computed column expression as if I had specified the case directly in the query?
What about if the computed column's expression were in a non-schemabound user-defined function?
EDIT
My example wasn't great since, as noted, the HasBalance column would not have a very good distribution of data. But ignoring for a moment the efficiency of the index itself, will the query processor basically treat the above query as shown below when selecting an index and choosing an execution plan?
SELECT ID, Name, Balance
FROM Customers
WHERE Balance > 0