sgmunson (12/14/2016)

---

Doug.F (12/14/2016)

---

sgmunson (12/14/2016)

---

Doug.F (12/14/2016)

---

Sonova...yep, I see where the hole is, in my logic =/

To be completely honest, I had rewritten it with ISNULL by the time I got back...

sgmunson (12/14/2016)

---

Doug.F (12/14/2016)

---

Sonova...yep, I see where the hole is, in my logic =/

To be completely honest, I had rewritten it with ISNULL by the time I got back to reading...

Just a word of caution.

Handle the quotes correctly on Scott's and Lynn's examples. You might end with strings with the value 'NULL' instead of NULLs for the columns. Or you...

Sonova...yep, I see where the hole is, in my logic =/

To be completely honest, I had rewritten it with ISNULL by the time I got back to reading the responses....

Grant Fritchey (4/12/2016)

---

Both plans are timing out. That means that, depending on the CPU cycles and estimates from the statistics, you could see different plans on different days on either...

Grant Fritchey (4/12/2016)

---

Doug.F (4/11/2016)

---

I was thinking that as well, so I went ahead and ran a:

UPDATE STATISTICS dbo.TableName WITH FULLSCAN

On all tables that are being joined with the SQL query,...

Grant Fritchey (4/12/2016)

---

Ron007 (4/11/2016)

---

compare execution plans in DEV and PROD

and use the query hint for index.... that using in prod.

the same index will use in dev if you put...

Jacob Wilkins (4/11/2016)

---

First things first: could you post the CREATE statement for the view referenced by the query (Stage_PLEMP_UniqueRecords_View)?Having said that, it seems to me that it's mostly a matter...

MAXDOP, MAXMEN, etc -...

Ron007 (4/11/2016)

---

compare execution plans in DEV and PROD

and use the query hint for index.... that using in prod.

the same index will use in dev if you put as shown...

John Rowan (4/11/2016)

---

We have similar issues from time to time in our dev environment. If rebuilding statistics/indexes does not help, it may be a major difference in the data...

I was thinking that as well, so I went ahead and ran a:

UPDATE STATISTICS dbo.TableName WITH FULLSCAN

On all tables that are being joined with the SQL query, unfortunately this had...