I'm not sure if this is a good idea:

WITH rCTE AS(

SELECT s.saleid, u.userid, b.businessunitid, b.name, b.parentbusinessunitid, 1 AS n

from ...

You're welcome.

However, do you understand the solutions?

You make it very difficult to help you. You only post a part of your code which doesn't seem to require a cursor or recursive query at all.

You might...

Are we supposed to take your word for granted...

jasona.work (9/25/2015)

---

Grant Fritchey (9/25/2015)

---

jasona.work (9/25/2015)

---

I've been wanting to pile into that topic, but keep restraining myself...

Hmm. Maybe we need to Godwin that topic, and bring in a comparison somehow...

Kristen-173977 (9/24/2015)

---

I recommend that you don't rely on the default size for varchar, there is some strange behaviour which will catch you out from time to time.

I use...

Use a CASE statement.

CREATE TABLE #Milestonetable(

JobNo INT,

MileStoneName CHAR(1),

ForecastDate DATE,

ActualDate DATE,

...

That comes from all the MAX() functions. Nothing to...

Or avoid the JOINs.

WITH CTE AS

(

SELECT id, num, COUNT(*) OVER(PARTITION BY id, num) dup_cnt

FROM @t

)

DELETE c

--SELECT *

FROM cte...

Remember that SELECT INTO will create a new table each time. To add the INTO clause, just include it before the FROM as you would with a normal query. You...

GilaMonster (9/24/2015)

---

Since the optimiser pushes predicates down...

I'd go up to four. 😎

T-SQL is a declarative language, which means that you're not telling the engine how to process the query, you just tell it what you want it to do. That means...

That's the way to do it. However, if you're hard coding the milestones, there's no reason to use the dynamic code. But that's the place where you would filter either...

If you can query the specific milestones, you can limit them.