Here's another suggestion:

WITH Table1 (ID, Val) AS

(

SELECT 201220, 0.5

UNION ALL SELECT 201219, 0.4

UNION ALL SELECT 201218, 0.4

)

...

Steve Jones - SSC Editor (12/16/2013)

---

I don't mind too much snow here, prefer it in the mountains.

It snowed last week, still snow on the ground, but supposed to hit 60F...

Are you perhaps looking for something like this?

WITH SampleData (Times, ACD, Other) AS

(

SELECT CAST('08:30' AS DATETIME), -12, -10

UNION ALL SELECT CAST('09:00' AS DATETIME), -48, -0

UNION ALL SELECT...

It appears that Monday morning without coffee isn't particularly conduciveto understanding requirements, so post removed.

pietlinden (12/12/2013)

---

Your table is really structured like that? What happens if you get more software packages? Does the table structure change? IF y

I think storing information using this...

Perhaps it is just a recommendation:

We recommend that you use catalog views because they are the most general interface to the catalog metadata and provide the most efficient way to...

happycat59 (12/12/2013)

---

dwain.c (12/12/2013)

---

Better to use sys.columns or sys.all_columns as information_schema.columns is being deprecated.

All the technical metadata exists in...

Better to use sys.columns or sys.all_columns as information_schema.columns is being deprecated.

All the technical metadata exists in there. ...

I agree with John that LAG would be pretty good for this:

WITH Aggregates AS

(

SELECT...

You might want to take a look at this article:

Condensing a Delimited List of Integers in SQL Server[/url]

Somewhere buried deep into it (perhaps 2/3s of the way down if I...

I have to agree with earlier posters that you don't need dynamic SQL for this, but let's assume that we can't see everything you do and it is really needed...

Is this what you're looking for?

WITH SampleData (dur_nano) AS

(

SELECT CAST(163691964 AS BIGINT)

)

SELECT dur_nano

,millseconds=(dur_nano/1000000)

,microseconds=(dur_nano/1000)%1000

,nanonseconds=dur_nano%1000

FROM SampleData;...

You should wrap your UPDATEs/INSERT/MERGE in a TRANSACTION and then do COMMIT/ROLLBACK consistent with your error handling.

Or you can skip creating the table all together and use a calendar generating FUNCTION instead:

CREATE FUNCTION [dbo].[GenerateCalendar]

(

...

I can see it now. Cornish pasty in one hand while the other furiously types in the 1M row test...