Just Learned - SQL Server - NEXT VALUE FOR (sequence) no longer supports UNION ALL

Getting Started with Adobe After Effects - Part 6: Motion Blur


	Just Learned

A collection of quick technology learning tips from what people around you learn every day


	Submit a tip


	Subscribe..

Home · Most Liked · Most Learned · Most Discussed · Silver Rated · Sections

SQL Server - NEXT VALUE FOR (sequence) no longer supports UNION ALL

Apr 30 2012 12:00AM by Sven Aelterman

At one point, I created a demo script whereby one could retrieve the next value in a SQL Server 2012 sequence and use that value in a UNION ALL clause. That worked up to and including CTP 3. It never worked with plain UNION. I never tested it on RC0, but now, in SQL Server 2012 RTM, this is no longer supported.

Read More.. [80 clicks]

Published under: SQL Server Tips · · · ·

Previous: 16 bit apps are not supported in 64 bit windows
Next: SQL Server - Secret behind restriction of maximum length of 116 characters for temp table names

Sven Aelterman

668 · 0% · 49

Liked

Knew

Learned

Incorrect

Interesting

Forgotten


Post this to my facebook wall
Tweet this
Like This
I knew this before
Thanks, I just learned it from you
Sorry, but this is not correct
Interesting, but not my area
I knew it but i have forgotten it


	Submit

Your Comment

Sign Up or Login to post a comment.

"SQL Server - NEXT VALUE FOR (sequence) no longer supports UNION ALL" rated 5 out of 5 by 9 readers

SQL Server - NEXT VALUE FOR (sequence) no longer supports UNION ALL

Your Comment