Viewing 15 posts - 38,581 through 38,595 (of 59,072 total)
jcrawf02 (5/6/2010)
ask people for topics they'd like to see, there may be things they're working on that they can use help with.
That's an outstanding idea. Just keep in mind...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2010 at 5:19 pm
Paul White NZ (5/6/2010)
Jeff Moden (5/6/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2010 at 4:48 pm
Paul White NZ (5/6/2010)
Ok, here's the quick 'n' dirty CLR aggregate:
Ooooohhhhh mmmmyyyyy ggggooooodddd... someone that actually knows what "//" is for.
Very well done Mr. White.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2010 at 4:45 pm
AspiringGeek-40457 (5/6/2010)
"The only thing worse than training everyone and having some of them leave is not training any of them and having them all stay."--Zig Ziglar
I love it...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2010 at 12:28 pm
sqlwars (5/6/2010)
I guess, I have done enough of DBA work, i better take a U...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2010 at 12:20 pm
I'll have to remember that as one of the things to check on when I install my nice new copy of 2k8 Dev Ed. Thanks, Peter.
Now that I see...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2010 at 6:39 am
RTaylor2208 (5/6/2010)
Also I modified the functions so I could provide 2 dates so I can calculate the time passed between them instead...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2010 at 6:36 am
Heh... actually, it was "cutting edge" at the time with Windows XP Pro and all. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2010 at 6:34 am
@ Paul,
Yep... I remember the "other" triangular join. You made it to be very fast but it still ended up doing the same number of reads. This one...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2010 at 6:32 am
In just about anything I've seen having to do with software, 99% of the people only know how to use 1% of the functionality. A lot of the new...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 5, 2010 at 11:37 pm
Contrary to popular belief, the reads are usually the result of an index or two on the table you're inserting into. There could also be a trigger on the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 5, 2010 at 11:30 pm
Yes... that would work if there were a date column. The posted problem is quite a bit different... the OP has no date...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 5, 2010 at 11:28 pm
Clive,
First, thanks for posting the test setup... makes it so I can concentrate on your problem and give you a coded answer almost as soon as I see the post.
See...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 5, 2010 at 11:25 pm
Something that people either aren't aware of or have forgotten... the option of in-house training by the resident experts is a powerful tool that's frequently over looked. It...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 5, 2010 at 11:05 pm
Mark-101232 (5/5/2010)
Try this
CREATE FUNCTION dbo.InsertCommas(@s VARCHAR(100))RETURNS VARCHAR(100)
AS
BEGIN
SELECT @s=STUFF(@s,Number,0,',')
FROM master.dbo.spt_values
WHERE Number BETWEEN 2 AND LEN(@s) AND type='P'
ORDER BY Number DESC
RETURN @s
END
GO
DECLARE @s VARCHAR(100)
SET @s='W'
SELECT @s,dbo.InsertCommas(@s)
SET @s='ABWI'
SELECT @s,dbo.InsertCommas(@s)
SET @s='AW'
SELECT @s,dbo.InsertCommas(@s)
I love it...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 5, 2010 at 10:35 pm
Viewing 15 posts - 38,581 through 38,595 (of 59,072 total)