Home Dashboard Directory Help
Search

Implement Window Functions in SQL Azure by JohnArcherRisk


Status: 

Closed
 as Won't Fix Help for as Won't Fix


7
0
Sign in
to vote
Type: Suggestion
ID: 787199
Opened: 5/18/2013 9:03:53 AM
Access Restriction: Public
0
Workaround(s)
view

Description


The introduction of Window Functions in SQL Server 2012 is a powerful and tremendously useful feature missing from SQL Azure. I recently developed an on-premise solution in SQL Server 2012 making heavy use of these new functions and was unable to migrate this solution to SQL Azure. Any idea as to when SQL Azure will support window functions?
Details
Sign in to post a comment.
Posted by Greg Low - Australia on 8/12/2013 at 9:59 PM
Please reconsider the decision about not implementing these.

One of the touted benefits of changes to SQL in Azure was the move to a single code base. If it's the same code base, why is there complexity in enabling window functions? They will allow for much more elegant and efficient code. Efficient code is what we all want in a shared environment like Azure.
Posted by SAinCA on 6/18/2013 at 10:50 AM
Doesn't this beg the obvious question, "If Azure is a flagship Product for MS and these are 'known' deficiencies that many, many apps use, WHY are there 'no plans to enable those in SQL Azure'?"

On-premise or private cloud (hosted, not using Azure) are our choices for "real" apps, then... "Real" = "full blown, as functional as an in-premise app".

Do not understand this decision! Especially do not understand it in wake of the pronouncement that "you will see new features first in Azure". Big Deal! If we don't have the old features, knock yourselves out developing new ones for Azure - at least they might be prime-time-ready when they get into the "real" Product! (SQL Azure = QA Test-bed AFAIC)
Posted by Microsoft on 6/18/2013 at 8:47 AM
Hello John,
Thanks for your feedback. We are aware of the missing SQL Server 2012 features and at this point we have no plans to enable those in SQL Azure.

--
Umachandar, SQL Programmability Team
Sign in to post a workaround.