... and then you probably still missed some :P.

RBarryYoung (2/6/2009)

---

Lowell (2/6/2009)

---

i've got a stored proc i made that i named sp_getDDL, which trolls thru the table definition and it's columns and builds the script for the table;...

I'd go the complete opposite. If the data requiresa unique index (for data quality), then go ahead and create the index. I wouldn't do a unique index just...

Alvin Ramard (2/5/2009)

---

It is your experience why you will see me continue to try and help people even when it seems pointless to continue. It is those times where...

You can't,it has to be done at the stored procedure execution time. The table is destroyed after that.

You could go to ##temp which makes it global, but also limits...

You lucky basta*d, I can,t find a single youtube video on the subject... what is the world comming to?? :alien:

Use your mind's eye... no need to use your actual eyes to post messages here. God knows that I'm unconsciously typing when I'm at my best!

Ah!, learn something new everyday :P.

That's a good it depends. There would need to have a buttload of traffic on that table to cause tempdb to crash or become...

I think I'd go with the instead of triggers... if it saves me a full clustered index rebuild.

I don't know, maybe do a manual import and then delete the dupes??? That's not the way I'd do it, but who am I to say something on that...

Not here, how about star trek... any series?

Ok, I'll join for a while...

I wonder what Joe Celko would answer to those questions :w00t: :Whistling:

That's the whole idea... it's already self-aware by now (go back a couple 100 posts).

We're making our own version of skynet... with all the whizbang...

DBA is his avatar,veteran is because he has over 300 posts. That level is not garanteed to reflect skill...