I'm less worried about the points, though who doesn't like to have more points? 😉

What I am more worried about is that people who answer the question and get it wrong, or right, might take the answers at face value and not look at the discussion, so they will assume that non-persisted computed columns always use more resources, which means you probably shouldn't use them.

It, also, means that there is a different solution to the problem that does use fewer resources, and it would be nice if someone can share what the other solution(s) is/are.

For example as someone else mentioned your non-persisted computed column may use a non-deterministic formula and so you can't persist it.

For example:

CREATE TABLE dbo.Sample

(ID INTEGER PRIMARY KEY,

Post_Date DATETIME,

Ins_Aging_Date DATETIME NULL,

Pat_Aging_Date DATETIME NULL,

Age AS DATEDIFF(DAY, COALESCE(CASE WHEN Ins_Aging_Date < Pat_Aging_Date THEN Ins_Aging_Date ELSE Pat_Aging_Date END, Post_Date), GETDATE()));

Yes, you could let the client calculate the age, but then you are sending three date fields over the network instead of a single integer if all the client wants is the age. (And you have to maintain the formula in a different and possible multiple places.)