Viewing 15 posts - 47,491 through 47,505 (of 59,102 total)
Heh... the problem with the indecision that some face as to who to vote for is simple... which idiot will cause the least amount of damage? 😛
If you want...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 9:51 pm
There's virtually no difference between a JOIN and an IN (subquery)... they will both create the same execution plan and execute within milliseconds of each other... unless there's a correlation...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 9:18 pm
Matt Miller (10/31/2008)
"Must look Eye"
Heh... yeah... I forgot to add that on... 😛 So many cars... so little wax. :hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 9:09 pm
Muralidharan Venkatraman (10/31/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 9:02 pm
Nicely done! And thanks for the feedback especially on the performance/durations.
My only concern is the BEGIN/COMMITs you have for Stages 1 through 4... the [CPMTEST].[XJASN4N].[tblCLS_OFSA] is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 8:50 pm
ry.rith (10/31/2008)
that you tell me about the solution.
I also do the same of yours to complete the crosstab-report, but something that i want is to know why it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 8:22 pm
Heh... I've just gotta agree with that! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 8:05 pm
juergen.kessler (10/31/2008)
@Seth: Sorry Seth, will follow you next time.
If you do it this time, you'll actually get a tested answer... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 7:57 pm
jack_hc (10/30/2008)
I am facing a problem to extract data from a table, the table contains over 41k records, and some of them(>5k) share same column value, now what i am...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 7:45 pm
Mark Rissmann (1/30/2007)
IF UPDATE(VendorCode)
BEGIN
UPDATE vendor SET vendorcode=inserted.vendorcode
FROM inserted JOIN deleted ON inserted.vendorID=deleted.vendorID
WHERE (inserted.vendorcode <> deleted.vendorcode) AND (inserted.iscopy=0) AND (inserted.ID =...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 7:37 pm
Search the web for "CDONTS"
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 7:35 pm
It's a good thing to have, anyway... make a Calendar table based on the user inputs.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 7:25 pm
sam (10/31/2008)
e.g. row 4 and 5 have a common custnumber, amount and semester so i want...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 7:18 pm
dlongnecker (10/31/2008)
Hey everyone,I've got a table with a column of ints and I need to remove any discontinuity between them...
Although PW's post is spot on, I suspect there's a bigger...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 7:09 pm
anupamabr (10/31/2008)
thanks for your quick response ..eventhogh i changed the code it didnt work
Do you mean that you changed it to T-SQL?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2008 at 7:07 pm
Viewing 15 posts - 47,491 through 47,505 (of 59,102 total)