jacob sebastian (10/9/2008)

---

Agreed. But in such cases, having an index (even if it is NC) might be better than not having an index (even if there is an RID lookup)....

Holy moly! Thanks for posting that. It's always good to see the before'n'after.

Oh... one more thing... since you added and then deleted columns from the "real" table instead of using a temp table as a driver, you should probably run a DBCC...

True, but if it's not a Clustered Index, you'll also get an RID Lookup or a KEY Lookup. Now, on small tables, that doesn't mean much. But on...

Craig, BTW... how many rows was this for?

craig (10/9/2008)

---

Thanks a million Jeff

Using your script as a basis, you turned a 26+ hour process into 32 second process.

This is the code I'm now using

-- Add Column for...

Heh... I agree... but in a data file?

As a side bar, this is why I hate certifications. They mean nothing because you can get the answers to most of the questions one way or the other...

I agree with Gail... spend the 50 smackers and buy the Developer's Edition... you won't be sorry.

Actually, the SELECT * is pretty much going to blow any chances of real performance because the index will never do a seek.

Heh... the point is that Interviewer's ask some of the darnedest questions to find out if you really know instead of just memorizing a list of "interview questions". 🙂

chintan kotwal (10/9/2008)

---

Hello Everyone,

I was reading an article, and in that article as one of the rules for the database architect being 'Every table has a Primary Key'.

My question: Would...

Heh... I agree... this is what cursors are for...

...but then you'd have to admit to actually putting one in production. 😛

In SQL Server 2005, there is absolutely no reason to...

Two way street here... would you please post your solution? Thanks. 🙂

Sure you can do it. And, you don't have to write a lick of T-SQL to do it... Enterprise Manager will write all of the code for you.

Open Enterprise...