Viewing 15 posts - 47,821 through 47,835 (of 59,095 total)
mahesh.kumar (10/9/2008)
I have a updation on a datefiled for everyminute in all the records hence if i create a index on datefield wont it give a problem in writing..
Thanks &...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 11:23 pm
jacob sebastian (10/9/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 11:20 pm
Holy moly! Thanks for posting that. It's always good to see the before'n'after.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 11:18 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 10:23 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 10:19 pm
Craig, BTW... how many rows was this for?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 9:56 pm
craig (10/9/2008)
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 9:56 pm
Heh... I agree... but in a data file?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 9:53 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 9:49 pm
I agree with Gail... spend the 50 smackers and buy the Developer's Edition... you won't be sorry.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 9:28 pm
Actually, the SELECT * is pretty much going to blow any chances of real performance because the index will never do a seek.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 9:26 pm
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". 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 9:23 pm
chintan kotwal (10/9/2008)
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 8:53 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 8:44 pm
bharathi (10/9/2008)
I found it myself...Thankss a lot anywayz...
Two way street here... would you please post your solution? Thanks. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 8:21 pm
Viewing 15 posts - 47,821 through 47,835 (of 59,095 total)