expression in BETWEEN clause of the RANGE

Question

0.00/5 (No votes)

See more:

SQL-Server-2008R2

Hi All,

I am trying to convert following Oracle query to SQL Server and having issues in defining calculation in the BETWEEN of the PARTITION.

ORACLE Query:
SELECT  
  head.acct_unit, head.company,head.role_id,    
   AVG(head.HEADCOUNT) over 
      (partition by head.acct_unit, head.company,head.role_id
       order by head.posting_month 
       range between  head.posting_month - trunc(head.posting_month,'YYYY') PRECEDING and current row)  YTD_HEADCOUNT
FROM
TABLE_A head

SQL Server:

SELECT  
  HEAD.ACCT_UNIT, HEAD.COMPANY,HEAD.ROLE_ID, 
  AVG(HEAD.HEADCOUNT) OVER 
      (PARTITION BY HEAD.ACCT_UNIT, HEAD.COMPANY,HEAD.ROLE_ID
       ORDER BY HEAD.POSTING_MONTH 
       -- RANGE BETWEEN DATEDIFF(dd,DATEADD(yy, DATEDIFF(yy,0,HEAD.POSTING_MONTH), 0),HEAD.POSTING_MONTH)
	   --	PRECEDING AND CURRENT ROW
	   )
FROM
TABLE_A head

Any help in this regard is highly appreciated.

Regards,
Shijith

Posted 26-Aug-14 21:43pm

Member 3977372

Updated 27-Aug-14 1:20am

sankarsan parida

v2

Add a Solution

Comments

coded007 28-Aug-14 8:02am

what is the problem you are getting

Suvendu Shekhar Giri 4-Jan-15 14:09pm

As far I know, unfortunately UNBOUNDED PRECEDING, UNBOUNDED FOLLOWING, CURRENT ROW etc keywords are not available with SQL Server 2008 R2. These are introduced with SQL Server 2012. So, may be you need to find an work around to resolve your problem without using these keywords. :)

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)