Viewing 15 posts - 38,551 through 38,565 (of 59,072 total)
jayanp (5/7/2010)
Yes.Need to add in to a stored procedure.Since I did not get any reply, I found out the solution myself.
Thanks anyway.
I understand the disappointment of "no reply", but...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2010 at 11:37 am
Cory Blythe (5/7/2010)
Some of the more common uses would be find all Values of Zip2 within 10 miles of Zip1 etc.
One of the very useful performance tweeks here is to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2010 at 11:32 am
Cory E. (5/7/2010)
This is why we are looking for requirements.
Heh.... I understand the lesson in progress but I thought the requirements were actually pretty clear on this one. From...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2010 at 11:19 am
Heh... I just wanted to know if it worked for you. :blush: Thanks for the compliment, Clive.
Just a followup warning... don't take any shortcuts or deviate from the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2010 at 11:03 am
RAJ GOPAL (5/7/2010)
HiRefere to this link
http://www.simple-talk.com/sql/t-sql-programming/concatenating-row-values-in-transact-sql/
What I really hate about articles like that is it's mostly just a list of methods someone collected and posted without any reasonably sized...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2010 at 10:46 am
Rajesh Arra (5/7/2010)
Thank you all, will work on it and get back to you if needed
Better than that, get back to us with how you ended up implementing it. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2010 at 7:36 am
Damn... great idea. This is a "bin stacking" problem and I know people that would kill to have this as a truly scalable solution. The solution, as...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2010 at 7:34 am
Thanks. That's just what I needed.
Like I said, UNION ALL the 3 queries and do a simple Cross Tab... this will do what you want it to...
SELECT preagg.Dept,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2010 at 1:00 am
Chris Lindley (5/7/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2010 at 12:24 am
CirquedeSQLeil (5/7/2010)
eric_russell 13013 (5/7/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2010 at 11:26 am
Agile (5/6/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2010 at 7:42 am
Grant Fritchey (5/7/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2010 at 7:37 am
Heh... my colorful name for certain types of code is likely obvious at this point in history...
[font="Arial Black"]RBAR[/font]
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2010 at 7:26 am
I don't know about the "deep internals", but a scalar function has the same affect as calling a stored procedure where an iTVF used with a CROSS APPLY makes for...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2010 at 6:53 am
ziangij (5/7/2010)
great article... thank you 🙂
You're welcome. Thanks for both the visit and the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2010 at 6:32 am
Viewing 15 posts - 38,551 through 38,565 (of 59,072 total)