Post reply

get nextid for non-identity column

  • February 14, 2008 at 1:50 pm

    #778580

    I think if you use my idea of what Jeff calls a 'Sequence Table' plus what he refers to as a propietary UPDATE, you should be in good shape.

    But I would evaluate it in terms of how many inserts you expect. Basic question: is it more or less than 1 per second?

    I have used this approach in an application but it's definitely not in the 'more than 1 per second' category.

    It's not that difficult to stress-test this by running inserts from 3 or 4 computers simlutaneously. This should give you an idea of the throughput your solution can handle.

  • February 14, 2008 at 8:02 pm

    #778677

    In other words, please see the following URL...

    http://www.sqlservercentral.com/Forums/Topic418139-8-1.aspx#bm418200

    ...and don't worry... provided you call it correctly and learn how to use the "Increment" as I've laid out in the URL above, it's very rugged and can take thousands of hits per second...

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 2 posts - 16 through 16 (of 16 total)

You must be logged in to reply to this topic. Login to reply