Viewing 15 posts - 45,151 through 45,165 (of 59,101 total)
J (2/16/2009)
Cast the output as CONVERT(VARCHAR(DesiredColumnWidthHere), long_column_name) AS long_column_name.Interesting.
So I suppose this is more efficient than SUBSTRING ?
Regards
Sorry to use the ol' cliche`, but it depends... sometimes SUBSTRING won't...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2009 at 10:45 am
David Jackson (2/16/2009)
Ours is not to reason why, but to do and die... :Whistling: 🙂
Heh... I really hate it when THAT happens. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2009 at 10:42 am
sunny1_liu (2/15/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2009 at 10:39 am
AFCC Inc. Com (2/15/2009)
Now if it is blinds they are priced by width and height, "a grid"
I have attached an example grid that is used by the blind manufacturers and...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2009 at 10:26 am
Heh... well said. Actually, I hated the old outer join notation... especially since Oracle and SQL Server did it exactly the opposite from each other.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2009 at 10:20 am
Derek Dongray (2/16/2009)
bitbucket (2/13/2009)
shhh tell no one, but heck it was better than using a slide rule to do the calculations.
I still have my slide rule and can even remember...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2009 at 10:16 am
Derek Dongray (2/16/2009)
Take a rat. Drop it in a maze. If it takes the wrong path, it gets shocked. If it takes the right path, it gets...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2009 at 10:14 am
Bruce W Cassidy (2/15/2009)
Jeff Moden (2/15/2009)
Anything that won't even allow for more than a 30 character object name certainly isn't the most flexible of the two.
[font="Verdana"]Okay, now I have to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2009 at 9:58 am
Bruce W Cassidy (2/15/2009)
Jeff Moden (2/15/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2009 at 9:55 am
sumit-saini (2/15/2009)
SELECT id,
days,
days - COALESCE((SELECT max(days)
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2009 at 9:38 am
400 Million rows? Consider partitioning that bad boy.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2009 at 9:07 am
I'm sure there's a better way than the code I modified to go from 2k to 2k5... I haven't nailed down all of the new system views that came with...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2009 at 8:44 pm
Nice job, but recursion is actually slower than a cursor.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2009 at 8:05 pm
Heh... simple... the software was the very fabric of their business {visibly and audibly gagging at the terrible pun} 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2009 at 8:02 pm
... and, no.... again, I don't need to know how to solve the problem... I've done it at least a half dozen times with the "running total update" and once...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2009 at 7:56 pm
Viewing 15 posts - 45,151 through 45,165 (of 59,101 total)