Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
lazerath
Constraint Violating Yak Guru
343 Posts |
 Posted - 2014-11-19 : 16:06:27
|
| Hello all,Has anyone worked with the new SEQUENCE objects and specifically making range requests (sp_sequence_get_range)? We have seen some odd behavior where this is not giving unique values under concurrent load. Here's a Microsoft Connect ticket describing it further:https://connect.microsoft.com/SQLServer/feedback/details/1033916Looking for any confirmation or thoughts on this. Thanks in advance! |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-11-19 : 16:18:22
|
| This sounds like something you should post on Twitter using the #sqlhelp hashtag as many MCMs, MS engineers, SQL Server experts help answer SQL Server questions there. Put the link into a tiny url thingy to save on characters. I think you'll get back some good feedback.I can post it for you if you don't have a Twitter account, but I think it makes most sense for you to post it so that you can answer any questions.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
 |
|
|
lazerath
Constraint Violating Yak Guru
343 Posts |
Posted - 2014-11-19 : 17:13:01
|
| Good suggestion. Thanks Tara. |
|
|
|
gbritton
Master Smack Fu Yak Hacker
2780 Posts |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-11-20 : 11:43:47
|
quote:
Originally posted by gbritton
Did you post this:https://connect.microsoft.com/SQLServer/feedback/details/1033916?Sounds like a bug to me
Yes he did. It's in his post.  Agreed that it sounds like a bug. Lazerath, you should probably open a case with MS rather than just a Connect item. If it's determined to be a bug, then there is no charge for the case.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
lazerath
Constraint Violating Yak Guru
343 Posts |
Posted - 2014-11-20 : 13:32:09
|
| A coworker posted this. Sounds like a bug to us too. Good call on submitting a case, we will do that. |
|
|
|
lazerath
Constraint Violating Yak Guru
343 Posts |
Posted - 2014-12-05 : 14:53:19
|
All, this was the response from Microsoft:quote:
I wanted to confirm that this is a known issue with SQL 2012 and SQL 2014. In SQL Server 2012 it will be fixed in SQL Server 2012 SP1 CU14 and for SQL 2014 it will be the next CU after CU14 is released.
|
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-12-05 : 15:01:42
|
quote:
Originally posted by lazerath
All, this was the response from Microsoft:quote:
I wanted to confirm that this is a known issue with SQL 2012 and SQL 2014. In SQL Server 2012 it will be fixed in SQL Server 2012 SP1 CU14 and for SQL 2014 it will be the next CU after CU14 is released.
Thanks for the follow-up!Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
Non-unique keys w/SEQUENCE & range allocation