Viewing 15 posts - 56,161 through 56,175 (of 59,070 total)
Adam...
What do you want to happen if the amount of data exceeds the VARCHAR(250) column you've outlined?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2007 at 6:38 am
Simply stated... YES... that's exactly the way to do it. As Serqiy pointed out, there are some performance issues that will resolve AND there are other benefits down the line, as well.
There are...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2007 at 6:35 am
Sure... it's definitely a trick... we needed some way to aggragate all of the "findings" to a single row for each ID/name. We also needed the some aggragate to wrap the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2007 at 6:18 am
Or, in your terms, Denby...
SELECT pd.KPAIDS_NO, pd.LastName,pd.FirstName,
MAX(CASE WHEN dl.Clinical_Diagnosis LIKE 'Lymphadenopathy%' THEN 'Yes' END) AS Lymphadenopathy,
MAX(CASE WHEN dl.Clinical_Diagnosis LIKE 'Candidiasis%' THEN 'Yes' END) AS Candidiasis,
MAX(CASE...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2007 at 12:00 am
This exact same problem has appeared a couple of times now... starting to look a lot like homework... please post the code you've tried and then we'll help you figure...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 9:43 pm
Jin is correct... if you want multiple variable returns, one of the preferred mthods is to us sp_ExecuteSQL... and Books Online is the place to learn how to do that.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 7:44 pm
Heh! Now THAT's useful info!
You just talked me into putting nice sharp metal edges on it ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 7:36 pm
Ya gotta trust me on this one, Ben... things like the following tidbit have been tested, tried, and trued by me and about a thousand other folks on this and...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 7:28 pm
Koji,
Thanks for posting your solution... THAT's what we like to see when folks get things working!
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 7:23 pm
Heh... know wurrees, Ed... A've bin nown too meke na tyyp-oh hear ond their, meself ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 7:22 pm
Heh... obviously not a "precise" number, eh? ![]()
After seeing all the stuff about rounding on these interminable threads, I've decided I'm not rounding anything...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 7:14 pm
Krissy,
How big are the hard-drives associated with the datafile? The other question would be, how many months or years does the current 60 gig of space used represent? The reason...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 7:09 pm
No...
Each temp table is actually named a bit differently but is transparent to the user... for example, if you have a temp table named #MyHead in a proc, each session...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 4:58 pm
Ok... first the "party line"
This type of formatting should NOT be done in SQL Server... it should be done in the GUI...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 4:47 pm
Already posted this on the PM you sent me... thought I'd share the solution I think you are looking for...
CREATE TRIGGER Flag_update
on table_A
for update
as
if Update (Table_A.[Date])
Begin
update table_B
Set Flag =...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 7:24 am
Viewing 15 posts - 56,161 through 56,175 (of 59,070 total)