Subject Re: Using stored procedure results in the WHERE clause
Author sboydlns
First, thanks for your suggestions.

If I use a COMPUTED column, any time I use SELECT * FROM OPS_STOP_REC that column is going to be evaluated. This would end up doing a lot of I/O in those cases where I don't care about the value of the computed column. Since I use SELECT * FROM OPS_STOP_REC quite a bit in other places I don't really see this as a viable option. Yes, I could just select those columns that I care about, but the list is quite long and it becomes a maintenance nightmare as new columns are added.

I could define a view except that I have several of these conditions that may be used in different combinations. In which case I would need a view for each possible combination.

Got to think about this some more.