Louis Somers

My feedback

  1. 122 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Upvotes: 278

    <=-=Feb 1 2008 7:18PM=-=>

    Thanks for the valuable suggestion.

    This seems more like adding the sequence support which we’re seriously considering for the next major release.

    Meanwhile, would using identity column help?

    <=-=Feb 2 2008 2:11AM=-=>

    It does not seem that you understood the request. This definitely has nothing to do with
    IDENTITY. I am less versed about sequences, but I don’t think they will cut it either. If you think
    it does, maybe you could provide an example? Take this problem: For the Orders table in
    Northwind, write a query that lists the number of orders for all days in 1997. The result set should
    include all 365 days, and list zero for days without a number.

    This is a typical problem where you need a table of of numbers (or dates). While it’s easy to
    create such a table, I argue in this request that…

    Louis Somers commented  · 

    This is quite a big deal, just look at all the effort to find the best way to do this at:
    https://stackoverflow.com/questions/10819/sql-auxiliary-table-of-numbers/2663232#2663232
    and again at
    https://stackoverflow.com/questions/1393951/what-is-the-best-way-to-create-and-populate-a-numbers-table/1407488#1407488

    Off course it should not be a real table, but a built in native keyword that acts like a table with a hardcoded 'column' of numbers on which we can join.
    Trying to update or insert to the table should generate an error.
    BIGINT should be large enough for most uses.

    Louis Somers supported this idea  · 

Feedback and Knowledge Base