Here is one of several of my Blog posts that talks about this: http://www.movingsql.com/dnn/Default.aspx?tabid=125&EntryID=190. In fact if you go my Blog site and click on the "Dynamic SQL" topic...

Heh. I did do a presentation on it. And I posted the presentation kit, including SQL code examples and Client code at my blog, here:http://movingsql.com/dnn/LinkClick.aspx?fileticket=pa1HXFdJ5Bs%3d&tabid=125&mid=911 But, I...

ziangij (2/19/2010)

---

thanks...

i just checked it out.. without indexes, update query takes 30 sec.

with the indexes in places, it takes 2 min !

RBarryYoung (2/17/2010)

---

I think that it depends on a number...

See, these are ALL much better answers than trying to change a system procedure. Here's another "insane" one: Write you own SSMS Add-in that modifies it's behavior to call...

Though it does seem to me that what this is really supposed to do is to just drop the NULL-valued clauses completely from the dynamic sql, rather than executing them,...

Kevin Rathgeber (2/18/2010)

---

...

One of the standards out there in application development is to use stored procedures for allowing the users to insert, update, delete or select data from a table....

Um, no. You should remember "Newbie", "dangerous" and "unnecessary". I would no more tell...

Kevin Rathgeber (2/18/2010)

---

RBarryYoung (2/18/2010)

---

Kevin Rathgeber (2/18/2010)

---

RBarryYoung (2/18/2010)

---

Kevin Rathgeber (2/18/2010)

---

RBarryYoung (2/18/2010)

---

Dynamic SQL is not preferred, but saying that it should be "avoided at all costs" is far too strong and just...

These last few lines of your dynamic query:

...

And (tEx.BoatID = 0 Or 0 Is Null)

And (tEx.EventID = 0 Or 0 Is Null)

And (tPh.Weight >= Or Is Null)

And (tPh.Weight...

Kevin Rathgeber (2/18/2010)

---

RBarryYoung (2/18/2010)

---

Kevin Rathgeber (2/18/2010)

---

RBarryYoung (2/18/2010)

---

Dynamic SQL is not preferred, but saying that it should be "avoided at all costs" is far too strong and just is not correct....

I'm trolling? Heh,...

Glad I could help! Note also that I have changed the wording of my reply slightly.

Add a line like "PRINT @strSQL", right before the "Exec (@strSQL)" line. Then run the procedure again and post the PRINT output for us.

Kevin Rathgeber (2/18/2010)

---

RBarryYoung (2/18/2010)

---

Dynamic SQL is not preferred, but saying that it should be "avoided at all costs" is far too strong and just is not correct. There are...

I would also guess that this is a "cut and paste" matter, from a query where tblExperience had the alias "tEx".