OMG!!! Table driven code! What a concept 😉

Nice job, Serqiy...

Paul (5/3/2007)

---

Forget my original question...

Make believe that this has nothing to do with cursors, stored procs or anything else. I just want to know if anyone has ever seen...

Heh... when are they going to get to the list I submitted, Steve?

Bob Fazio (9/12/2007)

---

The following does a much better job explaining when/why to use table variables.

Also, be careful not to get into optimization overload. I still suggest that you spend...

Normalize 'til it hurts! It'll save lot's of pain later on... kinda like the pain you're going through right now... 😉

Ouch! Brain freeze! You just reminded me of a girl I used to...

GilaMonster (9/29/2007)

---

MSDB is a perfect example of how not to design a database. Every time I have to get data from that DB I end up tearing more hair out....

Did someone say "loop"??? :blink: On a single row????? :sick:

Using a previous example where 5 decimal places are required to be padded with zeros...

DECLARE @i DECIMAL(10,5)

SET...

Sorry... temporarily lost my mind... I meant CreatedBy and CreatedOn... not "Modified". 🙂

You think it's better to store all data twice on insert?... Once "normal sized" in the original...

Thanks, Bob...

First, updating 500K or even a million rows in a single update probably isn't a problem... 20 million is a problem. If you do some testing, I think...

Hold on.... let me get my pen and write this one down in my "Why I don't let developers design views" book 😀

Why do you need a unique ID on...

It was removed because it was a really bad idea...;)

Like I said, stop trying to decrypt the whole table... encrypt the lookup criteria and do a normal join or WHERE...

Why do you think you need the extra overhead of RTRIM/LTRIM when converting Decimal to Varchar?

Heh... why sure, Remi... just look at the difficulties Steve is having trying to fix some of the problems with this "forum in a can" code that RedGate bought. ...

Sure... somehow they managed to save trailing spaces in NVARCHAR columns... Use DATALENGTH to check... some of the columns are defined as 100 characters wide... and even if they only...