Have you tried using a format that is not DATEFORMAT dependent?

The string '29/12/2011 12:00:00 AM' is probably being interpreted as the 12th day of the 29th month 🙂

For example:

'2011-12-29T00:00:00'

'2011-12-29'

'20111229'

See http://msdn.microsoft.com/en-us/library/ms180878.aspx#StringLiteralDateandTimeFormats

With the problem as stated, you don't need the join to employee. This gives the correct result without any joins:

DECLARE @Position TABLE

(

JobCode ...

I can reproduce this (using the script exactly as written) on SQL Server 2008 R2 developer edition, build 10.50.2789 (SP1 + CU3, latest available) on Windows 7 Ultimate x64, with...

Surprisingly enough, I got this one right...

Happy 1us (2012 in base-32).

BSavoie (12/31/2011)

---

I like that plan, but what would be the best way to enforce the the "two members per team" rule on the server side? Check for and prevent more...

This seems like exactly the sort of...

Duplicate thread.

http://www.sqlservercentral.com/Forums/Topic1228598-392-1.aspx

This is the sample data in a more usable format:

CREATE TABLE dbo.Example

(

[User] VARCHAR(50) NOT NULL,

[Action] ...

Jeff Moden (12/30/2011)

---

SQL Kiwi (12/30/2011)

---

drew.allen (12/30/2011)

---

Naming conventions are simply conventions. There is no right or wrong. As long as they are consistent and meaningful, it doesn't really matter...

drew.allen (12/30/2011)

---

Naming conventions are simply conventions. There is no right or wrong. As long as they are consistent and meaningful, it doesn't really matter exactly what convention you...

All very good. And yes, a single DATEDIFF is 'better' than three DATEPARTs.

I have a feeling I might be missing some subtlety here, but is this close to what you need?

DECLARE @Member TABLE

(

MemberID BIGINT NOT...

Absolutely. If the logic is not suitable for an in-line TVF, make it a CLR scalar function instead -...

mtillman-921105 (12/30/2011)

---

WayneS (12/30/2011)

---

Hmm. I think I need...