Viewing 15 posts - 33,811 through 33,825 (of 59,099 total)
opc.three (5/30/2011)
Jeff Moden (5/30/2011)
Are you suggesting that you want only leaf-level information no matter which part you ask for? 🙂
That's what I got out of it this time around but...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2011 at 11:24 am
David-155102 (5/30/2011)
Hi Jeff,I see your point; if I change the test data to the following then "Part G" is not returned when it should be :crazy::
Ok... and I'm not being...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2011 at 9:42 am
flash.rsn (5/29/2011)
I have a table tb1 with following datetime columns.
c1,c2,c3,c4,c5,c6,c7,c8,c9,c10......so on
A trigger will update the each column with following conditions.
e.g if last column having null/empty...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2011 at 12:54 pm
Steve Jones - SSC Editor (5/29/2011)
Jeff Moden (5/28/2011)
Steve Jones - SSC Editor (5/27/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2011 at 11:31 am
Gail's summary is spot on. For more information, start at the following URL...
http://msdn.microsoft.com/en-us/library/ms179316.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2011 at 10:50 am
David-155102 (5/26/2011)
Using "Part D" as the example the result would be the following components:Part X
Part W
Part Y
Gosh... what would you want if Part Z had more than just Part Y...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2011 at 10:30 am
If you were to also update a "LastModifiedOn" column for the row when you set the flag to "USE", you could mod your program to check for the time difference...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2011 at 10:14 am
Google is your friend... click the following link 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2011 at 10:01 am
BTW... you can also remove the DISTINCT. It serves no purpose because WHERE/IN stops at the first occurance it finds. The DISTINCT is just burning some extra clock...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2011 at 9:47 am
allmhuran (5/29/2011)
a simpler hd.returnNo is not null and hd.returnNo != ''
You can actually go even simpler and faster because it only has one decision to make...
hd.returnNo > ''
But neither...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2011 at 9:41 am
Jake Shelton (5/26/2011)
...there are aspects of my new field that take time to develope,...
If you stated it, I'm sorry I missed it. Which new field did you jump...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 28, 2011 at 10:22 pm
Roy Ernest (5/27/2011)
GSquared (5/27/2011)
SQLkiwi (5/26/2011)
Steve Jones - SSC Editor (5/26/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 28, 2011 at 10:10 pm
Roy Ernest (5/27/2011)
I had a great time hanging around with...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 28, 2011 at 10:03 pm
Steve Jones - SSC Editor (5/27/2011)
Now we got the $27k Prius in '07, but got a $1500 tax credit and saved a ton of gas.
What did it do to your...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 28, 2011 at 10:01 pm
I don't know for sure but I'd almost bet the number of reads and writes being different from run to run are because I'm writing to disk and SQL Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 28, 2011 at 9:54 pm
Viewing 15 posts - 33,811 through 33,825 (of 59,099 total)