Thanks for the feedback on what you did.

Heh... I sometimes forget just how lucky I am... we "clone" the database everynight at midnight to a "do what you want, users"...

Now, that's a pretty good idea. Thanks, Steve.

I agree that they shouldn't be abuse or cursed at... heh... just quietly fired 😀

Karthik,

You, of all people, should know better... get onto the Microsoft web site and look for "What's new in" each of the different versions. Do some of your own...

I've gotta disagree with you there, ol' friend. ...

And, I gotta disagree... this isn't a triangular join... internally generated rows to not form the classic triangle. No table has more rows spawned than either of the original...

Oh yeah... just got me thinking...

Ok... you certainly shouldn't post that data... it contains private information and understood about the source code.

Here's the real key... you're using an application to insert 2.2 million rows, one...

On second thought, it's not a triangular join... for a count of 3, a triangular join would generate...

1

1 2

1 2 3

... to get the count... 6 rows total. This...

Heh... yeah... it is... 😛

Difference is that all rows it touches are generated in the output... nothing wasted. Like I said in the article, they're not all bad...

... I...

Heh... what happened to 150 questions?

The real problem with the way you wanted to do it is that if most of your questionaires only have 50 questions and you have...

It sounds like you're getting data from a file, cleaning it up, and then inserting it into a database... For 2.2 million rows, this shouldn't take more than a minute...

Heck yeah there would be performance issues... performance would increase because you could properly index it 😀

simon.letts (1/9/2008)

---

Thanks for that effort, it looks very complicated for what I want though.

To make it easier ...lets say that I just have a table with just one column, trans_code...

You would get a lot of help if you'd at least identify what it is what you want to do... 😉

But I understand... sometimes you're in a bit of a...