OK try this, may work better as no conversion to datetime required

SELECT

CAST(TS_TIME_ASSIGNED / 86400 as varchar) + ' days ' +

CAST((TS_TIME_ASSIGNED % 86400) / 3600 as varchar) +...

If you are using DTSrun to execute the package (eg in a scheduled job), it will output any errors which includes the row(s) and column(s). If it is a scheduled...

DECLARE @date datetime

SET @date = DATEADD(second,508621,0)

SELECT

CAST(DATEPART(dayofyear,@date)-1 as varchar) + ' days ' +

CAST(DATEPART(hour,@date) as varchar) + ' hour ' +

CAST(DATEPART(minute,@date) as varchar) + ' mn...

There are several threads discussing this subject and I think the concensus is that the following are the most efficient to avoid the use of CONVERT.

CAST(DATEADD(day,DATEDIFF(day,0,@dateField),0) as smalldatetime)

CAST(CAST(@dateField as int)...

Now do you have anything for the required formatting other than concatenation ?!?!

STUFF(CONVERT(varchar,DATEADD(s, epochCol,'19700101'),120),1,10,CONVERT(char(10),DATEADD(s, epochCol,'19700101'),103))

SELECT DATEADD(s,[epochcolumn],'19700101')

assuming that your 'Date Zero' is 01/01/1970

@@DATEFIRST is dependant on the Language setting for your login, check the Language settings for the login that is running the job and the login you use for QA,  e.g.

@@DATEFIRST...

Well, the syntax for that doesn't check out. Incorrect syntax near CASE

Don't see why, it worked fine...

Do you mean

select TimeCol, DescriptionCol

from myTbl

order by

case @sortBy

   when 'Time' then convert(varchar(50),TimeCol,121)

   when 'Description' then DescriptionCol

end DESC,

case @sortBy

   when 'Time' then DescriptionCol...

what do you mean -> Item.Qty be repeated for a [Date]

UNION will suppress duplicates as in...

SELECT [Date],ItemA AS [Item],QtyA AS [Qty]

FROM

UNION

SELECT [Date],ItemB,QtyB

FROM

UNION

SELECT [Date],ItemC QtyC

FROM

How many Item's are there, is it a fixed number?

Can Item/Qty be...

we tried releasing the recordset (RS = Nothing)

Try closing the recordset (and any additional ones if...

Not if the output is > 8000 bytes

The problem is due to the consumption of the output recordsets, as in the following from MSDN

"If a command returns a single result...