I don't think you need the 'lastid' field... you could've done the same without it, right?

Yes, it should always contain the same value as the id column. This UPDATE thingy...

This question pops up every now and then, and IIRC the answer was always the one Remi gave. You can't do this with QA, AFAIK.

Read BOL closely. The T-SQL CASE expression is not like CASE in other programming languages. But it's certainly one of the most powerful tools in SQL.

RSS feed would be a nice goodie. 

One might be inclined to think, that this is presentational stuff done best at the client. Anyway, piggy-backing on Remi, here's another method

SELECT REPLACE(STR(@x*100,11), ' ', '0')

for the lazycoder.

Have you tried that also on the Google Groups?

<A href="http://groups.google.de/groups?q=first+date&hl=de ">http://groups.google.de/groups?q=first+date&hl=de

Addendum: Got yesterday a book by CJ Date on my desk to review. It backs up, of course, what Joe already said. Because the correct pronounciation is Ess-Cue-El you say...

I like to think that converting to string and back is not the best sultion possible. These should be faster:

SELECT CAST(SUBSTRING(CAST(GETDATE() AS BINARY(8)),1,4) + 0x00000000 AS DATETIME)

SELECT CAST(CAST(SUBSTRING(CAST(GETDATE() AS binary(8)),1,4)...

Nice to know that you agree with me.

Have a look at NOT EXISTS in BOL.

Personally I would rather prefer to do

 SELECT DATEADD(minute, -DATEPART(minute, TempTime) % 5, TempTime) AS StartingInterval,

  AVG(Temperature) AS AverageTemperature

  FROM temperatures

  GROUP BY DATEADD(minute, -DATEPART(minute, TempTime) % 5, TempTime)

on the server...

Well, we're talking about more than 100 databases, with thousands of stored procedures built over the last 5 years by 15 or so developers, so the structure of them varies...

There might be a tool already existing, but a start might be to adopt a good commenting style within your procedures when they are created.

What is this

order by max(CONVERT(decimal(19,4), DATA_VALUE_ )) desc

supposed to do along with a TOP 1 ?

2005/a/b/001

Life would be easier when you would break this into separate columns. Is there a specific reason why you want to maintain such a sequence at all within your data?