Here are some other solutions. FWIW:

DECLARE @geburtstag DATETIME

SET @geburtstag = '19830908'

SELECT

 DATEDIFF(yy, @geburtstag, GETDATE()) -

 CASE

  WHEN (MONTH(GETDATE()) * 100 +

  DAY(GETDATE())) <

  (MONTH(@geburtstag)* 100 + DAY(@geburtstag))

  THEN 1 ELSE 0

 END

SELECT

 (CAST(CONVERT(CHAR(8),GETDATE(), 112)...

Can it be you have a problem with normalization?

Now you come up with such a string. One of the most referenced article regarding...

Neither Noel's solution nor the one I posted are dynamic.

What is it that you're really after?

Always my last resorts are .../ Stored Procs

Interesting typo

What about some classics ?

http://mindprod.com/unmain.html

http://www.galisteo.com/gallant/humor/klingon1.htm

Back in the old days when we used stone knives and bear skins we didn't have these fancy schmancy text editors ad IDE's that color coded syntax.

The programmer actually...

While I'm with Noel on the obvious state of your data, I disagree with his solution. A cross join can be a performance killer when it come to larger datasets;...

Did I ever mention that I really hate this autoreplacement with this annoying smilies

It's been mentioned quite a few times, that UDF's are executed for each and every row. Here's the proof of concept:

USE northwind

GO

CREATE VIEW foolview

AS

 SELECT

  GETDATE() AS Jetzt

GO

CREATE FUNCTION fool_me()

RETURNS...

That's a _very_ broad question!

You might want to read up both terms in BOL as a starter and come back with question that will certainly arise from reading BOL.

http://www.sommarskog.se/dyn-search.html

To get the last day of a month one can use something like this

SELECT

DATEADD(DAY, -DAY(GETDATE()), CAST(CONVERT(CHAR(8), GETDATE(), 112) AS DATETIME))

AS Monatsultimo

However, using integer operations should be faster:

SELECT DATEADD(d,DATEDIFF(d,DAY(GETDATE()),GETDATE()),0) AS...

You should post some input data along with what it should represent. That might be more descriptive.

This is more of a workaround than an true solution. SQL Server evaluates 1.0 as a non money datatype (FLOAT or DECIMAL).

Here's a script by SQL Server MVP Steve Kass...

Look at the site I've mentioned here http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=129464

There you'll find the explanation why this won't work.