Heh no worries 😀

Post back if you get stuck.

Never mind. Try this:

SELECT @retvalOUT = CONVERT(TINYINT,x.OutputColumn)

FROM [dbo].[SLADCSchedule]

CROSS APPLY (

SELECT OutputColumn =

CASE @DayOfWeek

WHEN 1 THEN Sunday

WHEN 2 THEN Monday

WHEN 3 THEN Tuesday

WHEN 4 THEN Wednesday

WHEN 5 THEN Thursday

WHEN...

Here's the query generated by your very strange code:

Select @retvalOUT = Convert(TinyInt,Sunday)

from [dbo].[SLADCSchedule]

where ScheduleStart <= 'Apr 1 2012 12:00AM'

and ScheduleEnd >= 'Apr 1 2012 12:00AM'...

The word Yep is a link 😉

Yep[/url].

Much the same question was posted here and another three or four threads on ssc in the last two or three weeks. Chopping and changing threads in this manner is...

dwain.c (8/19/2013)

---

Not sure this is a particularly efficient way to do this but this might work:

SELECT set_id, product, attribute=CAST(item AS INT)

FROM (

SELECT set_id=MIN(set_id), product, allattributes

...

Hi Walton

How many sets will you have?

How many rows will each set have?

Thanks.

LinksUp (8/18/2013)

---

I think this is what you are after:

select d.name, d.packsize, doc.doctorname, doc.location

from Doctor_Prescribed_Drugs dpd

left join Doctor doc on dpd.doctorref = doc.doctorref

left join Drugs...

This looks straightforward. If you can set up the sample data as a CREATE TABLE/INSERT INTO script, I'm sure someone will help.

robert.gerald.taylor (8/19/2013)

---

ChrisM@Work (8/19/2013)

---

robert.gerald.taylor (8/19/2013)

---

You're doing a lot in you If/else, couldn't you do something like:

SET @start = COALESCE(@startdate, DATEADD(yy, -1, @endDate), GETDATE());

SET @end = COALESCE(@enddate, DATEADD(yy, 1, @startdate), DATEADD(yy, 1,...

robert.gerald.taylor (8/19/2013)

---

You're doing a lot in you If/else, couldn't you do something like:

SET @start = COALESCE(@startdate, DATEADD(yy, -1, @endDate), GETDATE());

SET @end = COALESCE(@enddate, DATEADD(yy, 1, @startdate), DATEADD(yy, 1, GETDATE()));

Seems cleaner...

Here's a CROSS APPLY VALUES version. CAV is a longhand UNPIVOT, it's a little...

Why are you posting this in a SQL Server 2008...

sgmunson (8/18/2013)

---

Boy, a typo sure can bite you (Ouch! :w00t: ), and once committed, keep biting... Poor Jeff... his bite took out his CMOS battery...

Anyway, you appear to...