I tried adding the index on Entry_Sequence on the Patient_Info_Fields table but it didn't use it.

Sorry, that's the wrong view definition. That's one I was playing with that didn't work. Here's the live version.

That's the table referenced in the...

Grant Fritchey (5/10/2010)

---

Robert Frasca (5/10/2010)

---

Grant Fritchey (5/10/2010)

---

GilaMonster (5/10/2010)

---

I'm probably not going to get a chance to look at this, got a lot of work this week. Maybe Grant feels like...

Grant Fritchey (5/10/2010)

---

I don't have...

Sorry. No coffee yet.

This is one you looked at Friday. I've added the "good" query plan as well.

GilaMonster (5/7/2010)

---

23 rows... How big are the rows? If all 23 will fit on a single page, then you're right, there's no point.

Have you tried the divide and conquer? Insert...

Thanks for the suggestion. That is the table with 23 rows in it and I tried re-working the view (to reference the primary key) that is doing the recursive...

Okay, this problem has taken on a new dimension. Even when I rebuild the statistics the query still performs poorly on one database but works fine on the seven...

Grant Fritchey (5/6/2010)

---

Robert Frasca (5/6/2010)

---

Grant Fritchey (5/5/2010)

---

Robert Frasca (5/5/2010)

---

My experience is that function references in the FROM clause, i.e. inner joins, usually dramatically outperform function references in the WHERE clause...

Grant Fritchey (5/5/2010)

---

Robert Frasca (5/5/2010)

---

My experience is that function references in the FROM clause, i.e. inner joins, usually dramatically outperform function references in the WHERE clause because the WHERE clause...

Thanks for the reply. I tried the recompile thing without luck. Even though we rebuild the indexes every night, the only thing that makes the problem go away...

Thanks for the tip, I will. I have the magazine but hadn't had a chance to look at it or the e-version yet.

My experience is that function references in the FROM clause, i.e. inner joins, usually dramatically outperform function references in the WHERE clause because the WHERE clause must execute the function...

Well, I just learned that it apparently WAS a statistics issue. The local dba ran an UPDATE STATISTICS TableA WITH FULLSCAN and the problem went away. He specifically...