Thank you Brad for your response,

CROSS APPLY should behave like INNER JOIN. And yet with aggregates it behaves like OUTER APPLY or LEFT JOIN. I am wondering if there...

"Instead of shrinking in one shot, try shrinking in small batches.. may be 2Gb at a time or even 1GB... "

Thank you for this advise. I did it in chunks...

I am aware that DB shrinking is resource intensive. This is not a reason to shrink DB ~2 days without success. DB size is not enormous. No other intensive processes...

This is not only one database I need to have on that drive.

Thank you very much,

These are a SQL statements I would like to use.

However, only version with CTE gives correct answer. I will check performance later since real query is more...

I am sorry I was not clear.

150 is interval between orders and not from current date.

You recheck path:

portion "E:\" does not look right.

Yes you are correct. Sorry I did not copy correctly.

SELECT c.custnum, c.firstname, c.lastname,

c.company, c.addr, IsNull(c.addr2, '') addr2,

c.city, c.state, c.zipcode,

c.email,

dhc.uf_GetPN(LTrim(RTrim(c.firstname))) sal

FROM dhc.cust c

JOIN

(SELECT TOP(100) PERCENT WITH...

CROSS APPLY is for table-valued functions. Function I use is scalar-valued. Problem is following:

query selects rows based join with orders table without user function; if user function is present,...