Viewing 15 posts - 46,696 through 46,710 (of 59,101 total)
mmiruru (12/10/2008)
This function worked perfectly for what I needed to do. Thank you very much for your help.
First, it's not nice to double post.
Second, the function may work perfectly for...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 8:51 pm
Heh... to heck with all that... start answering posts on this forum with code! 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 8:44 pm
Nicely done, Peter.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 8:40 pm
I don't know how you'd do it in SSIS, but here's the T-SQL solution...
--===== Create a place to hold test data and populate it.
-- Note...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 8:38 pm
Zeev Kazhdan (12/10/2008)
Instead of group by, you might think of OVER (PARTITION BY...)
Why?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 8:24 pm
... and let me know if you still need a variable for the date...
And, never use INT for such a conversion because it rounds up to the next day for...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 8:03 pm
Heh... "We don need no stinkin' cursors"... 😛 ... especially in SQL Server 2005. Look at all the difficulties you're having making one do the things you want....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 7:57 pm
Ron, just an FYI... the code came through with no carriage returns.
And thanks for the awesome compliment! :blush:
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 6:48 pm
Yeah, but why do you want to format the code is SQL? Unless you're formatting to write to a file, then you should let the formatting be done in...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 6:21 pm
ggraber (12/10/2008)
Jeff Moden (12/10/2008)
I already did such a comparison in Part 1 of this series, Goldie. 😉 Of course, I don't mind if someone else does a head-to-head comparison.
Jeff,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 6:07 pm
Madhivanan (12/10/2008)
Nice Article JeffHere is mine
http://sqlblogcasts.com/blogs/madhivanan/archive/2008/08/27/dynamic-pivot-in-sql-server-2005.aspx
Thanks for the feedback and the link, Madhivanan.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 5:22 pm
I already did such a comparison in Part 1 of this series, Goldie. 😉 Of course, I don't mind if someone else does a head-to-head comparison.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 5:17 pm
Heh... nah... I've got a couple of folks like that at work... they're actually pretty nice if you can get them to stop talking about their damned hump! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 5:13 pm
I concur... haphazard formatting is tough on anything that expects a consistant format. OPENROWSET and Text Linked Servers do a pretty job job there.
Of course, when you have haphazard...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 5:06 pm
Garadin (12/10/2008)
(I know I know, it makes it easier to comment out lines and such, but I still hate it)
I do put each...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 5:02 pm
Viewing 15 posts - 46,696 through 46,710 (of 59,101 total)