Jeff Moden (1/15/2009)

---

Okay, let's make it sore spots...

Not naming names which...

This is a double post. Please respond here

Please refrain from double posting. Most people that will try to help you monitor all the threads one way or another.

Michael Earl (1/15/2009)

---

Matt Miller (1/15/2009)

---

Steve Jones - Editor (1/15/2009)

---

Well it is steel, and likely move's fast in Gail's hands, but no, it's not a bike.

http://en.wikipedia.org/wiki/Katana

Got to play with sticks last...

Matt Miller (1/15/2009)

---

Steve Jones - Editor (1/15/2009)

---

Well it is steel, and likely move's fast in Gail's hands, but no, it's not a bike.

http://en.wikipedia.org/wiki/Katana

Got to play with sticks last night, Filipino...

Jeff Moden (1/15/2009)

---

dmc (1/15/2009)

---

Haha... I agree that truely portable code is almost impossible to achieve. 🙂 But working in an environment with multiple systems we try to make...

Garadin (1/15/2009)

---

dmc (1/15/2009)

---

True... it is slightly (very slightly) faster. And in billions of rows it could make a difference. But is it wroth compliance of standards and advantages...

Chris Morris (1/15/2009)

---

Grant Fritchey (1/15/2009)

---

Oh yeah, two bows in the house, one a flat native american style long bow and the other a d-shaped english longbow with a Victorian riser...

I've got a few maritial arts weapons here at home, no swords. My pistols, however, are not stored at home at the moment as my wife didn't want them...

Jeff Moden (1/14/2009)

---

No... and today pretty much stunk...

Only because I kept reading and responding to your posts while still trying to write my first post. Sorry, don't know how to do both at the same time...

Different subject, have you had a chance to test my code yourself? After my last test, I feel much better.

Okay, I'm ready for my logical look at why it isn't a bug in the REPLACE function. First, let us think in terms of your million row test tables,...

I would call the truncation without warning a possible bug, but I think we have seen that behaviour else where in SQL Server as well. The fact that REPLACE...

Without testing...

Okay, but why? I look at it this way, if I'm willing to put down my reasoning, I think it only right to ask you to support your side...