Justin Grant

My feedback

  1. 1,341 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    47 comments  ·  Azure Cosmos DB  ·  Flag idea as inappropriate…  ·  Admin →
    Justin Grant supported this idea  · 
  2. 4 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 76

    <=-=Apr 21 2009 9:51AM=-=>

    Thank you for your feedback. This is something that we would like to add to SQL Server and we will definitively be keeping it in mind for future releases!

    Again, thanks for your feedback!
    -Tobias

    <=-=Nov 4 2009 1:15PM=-=>

    Please implement ANSI SQL date math.
    DATEDATE —> INTERVAL (equivalent for datetime, datetime2, datetimeoffset)
    DATE + INTERVAL —> DATE (equivalent for datetime, datetime2, datetimeoffset)
    TIMETIME —> INTERVAL (range specified by application)
    TIME + INTERVAL —> TIME
    DATE + TIME —> TIMESTAMP (i.e., datetime or datetime2 in SQL Server; NOT timestamp; equivalent for datetimeoffset)

    There is no way (without conversion) to add values of the new date and time types.
    DATEADD is very limiting (only one datepart at a time).
    Conversions so often necessary now to work with date/time data clutter code and impact performance.

    <=-=Dec 18 2009 9:25AM=-=>

    This sounds like…

    Justin Grant supported this idea  · 
  3. 6 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 1

    <=-=Dec 28 2017 10:38AM=-=>

    Defect #11427260 has been filed with our Product group on your behalf – Karly Shockley

    <=-=Dec 28 2017 11:34AM=-=>

    Shared here…

    Transact SQL � Warning � �Type conversion in expression may affect �CardinalityEstimate� in query plan choice�
    https://learningintheopen.org/2017/12/13/transactsqlwarningtypeconversion-in-expression-may-affect-cardinalityestimateinqueryplanchoice/

    Justin Grant supported this idea  · 
  4. 8 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Justin Grant supported this idea  · 
  5. 10 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Justin Grant supported this idea  · 
  6. 11 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Justin Grant supported this idea  · 
  7. 2 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Justin Grant supported this idea  · 
  8. 2 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 7

    <=-=Mar 3 2017 10:54AM=-=>

    We understand this requirement. We had plan to add more types in STIRNG_ESCAPE to support quotes, CSV, xml, url escaping; however, this is currently on hold. Hopefully we will get more votes for this item.

    However, if OPENQUERY and OPENROWSET are the reason, maybe it would be better to propose to support parameters in these functions.

    Justin Grant supported this idea  · 
  9. 2 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Justin Grant supported this idea  · 
  10. 5 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Justin Grant supported this idea  · 
  11. 3 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 7

    <=-=Jul 2 2015 4:21AM=-=>

    Thanks, we are aware that there are problems with tooling, but for CTP3 we are focusing on programmability.
    This problem will be fixed after CTP3.

    <=-=Sep 17 2017 4:45PM=-=>

    This is still not fixed in 2016 SP1. What’s the status on this?

    Justin Grant supported this idea  · 
  12. 3 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 1

    <=-=Dec 15 2014 8:59AM=-=>

    Hello,
    After carefully evaluating all of the suggestion items in our pipeline, we are closing items that we will not implement in the near future due to current higher priority items. We will re-evaluate the closed suggestions again in the future based on the product roadmap.
    Thanks again for providing the product suggestion and continued support for our product.

    Jos de Bruijn – SQL Server PM

    Justin Grant supported this idea  · 
  13. 7 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 5

    <=-=Aug 5 2014 9:56AM=-=>

    Hello,
    After carefully evaluating all of the suggestion items in our pipeline, we are closing items that we will not implement in the near future due to current higher priority items. We will re-evaluate the closed suggestions again in the future based on the product roadmap.
    Thanks again for providing the product suggestion and continued support for our product.

    Jos de Bruijn – SQL Server PM

    <=-=Sep 2 2016 1:23PM=-=>

    We’ve worked to bring WordPress to SQL Server through our port known as Project Nami. But the number one issue we are running into with making plugins compatible with SQL Server is the lack of support for GROUP_CONCAT.

    Justin Grant supported this idea  · 
  14. 6 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Justin Grant supported this idea  · 
  15. 29 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 173

    <=-=Sep 27 2010 2:23PM=-=>

    Hi Itzik,
    Thanks for your feedback on WINDOW clause. We will consider it for a future version of SQL Server.


    Umachandar, SQL Programmability Team

    <=-=Mar 21 2011 8:27PM=-=>

    I’m currently migrating an established application from another database platform to SQL Server. There’s a big, powerful chunk of the app missing due to the absence of the WINDOW clause functionality.

    I wouldn’t even want to think of how to implement this type of processing in SQLCLR, if that’s even possible.

    And if WINDOW is standard SQL, shouldn’t it be included in the Microsoft product? Competitors have it.

    <=-=Mar 2 2012 1:18PM=-=>

    Reuse of Window Definitions with WINDOW Clause
    This has been rolled up into our “Window Aggregates Enhancements” DCR for future consideration. Thank you for reporting it. All the information you provided has been captured for future reference.

    Thanks,
    Marc Friedman

    <=-=Nov…
    Justin Grant supported this idea  · 
  16. 3 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Justin Grant supported this idea  · 
  17. 16 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 6

    <=-=Mar 3 2017 2:00PM=-=>

    We are aware that this is important missing feature; however, we have no plans to add this in the near future. We will keep this request in backlog to see how many votes will get.

    <=-=Jul 1 2017 7:03PM=-=>

    Can’t even remember how many times I’ve wished to have this in SQL server.

    If you want to get a somewhat realistic feel of how talked about this feature really is, you can check out the number of votes and more importantly views that this StackOverflow question has:

    https://stackoverflow.com/questions/1732613/how-to-declare-array-inside-sql-server-stored-procedure

    Unfortunately, not many people visit this website and participate in voting here so it’s not a reliable indicator of how much any particular feature is requested. Please consider moving to UserVoice. Visual Studio UserVoice for example has loads more activity.

    <=-=Jul 1 2017 11:17PM=-=>

    We totally understand that t-sql as a language itself is desigened to…

    Justin Grant supported this idea  · 
  18. 2 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    need-feedback  ·  3 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Justin Grant supported this idea  · 
  19. 146 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 72

    <=-=Mar 10 2016 11:26AM=-=>

    It’s a shame that this was submitted as just a “suggestion”. It should actually be listed as a “bug” because there’s only a comparatively small set of use cases where enumeration of the result set of elements is not important.

    <=-=Mar 11 2016 12:47PM=-=>

    I agree that an order column is required; one example use case is where two lists are passed in, and ordinal positions in one list correspond to positions in the other.

    <=-=Mar 11 2016 3:12PM=-=>

    Please see the related suggestion: STRING_SPLIT needs “RemoveEmptyEntries” option, like String.Split in .NET ( https://connect.microsoft.com/SQLServer/feedback/details/2462002/ ).

    <=-=Mar 12 2016 12:02PM=-=>

    This kind of function is primarily needed for de-serializing previously serialized arrays of values of any type format-able as text.
    I therefore recommend to have the result set of this function work excellent with this use-case.

    With de-serialized arrays there is a need to…

    Justin Grant supported this idea  · 
  20. 126 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Justin Grant supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base