Post reply

trapping large loops

  • December 12, 2003 at 5:13 am

    #160427

    Hi,

    I did something silly and let my app enter in 33,000 records into the database.I deleted them of course, but believe that these sql2k generated unique id’s are now gone forever.

    I was wondering if there is a way to put a breakpoint/trigger in my sql 2k database that will stop loops entering in more than a specific number of new IDENTITY columns.

    I’m not confident that I won’t make a similar mistake in the future.

    Thanks,

    Yogi.

  • December 12, 2003 at 7:50 am

    #485937

    quote:

    I was wondering if there is a way to put a breakpoint/trigger in my sql 2k database that will stop loops entering in more than a specific number of new IDENTITY columns.

    No, but you can reset the identity with DBCC CHECKIDENT. If other rows have been added after the gap was opened, you can change those values using SET IDENTITY_INSERT.

    --Jonathan



    --Jonathan

  • December 12, 2003 at 9:30 am

    #485981

    Cheers Jonathan.

    livin and learnin..

    yogi

Viewing 3 posts - 1 through 2 (of 2 total)

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