On Thu, Dec 10, 2015 at 6:10 AM, Alan Bourke <[email protected]> wrote:
> My understanding is that @@IDENTITY is scoped across all tables in the > current session, therefore if something else was, for example, bulk > updating another table or a trigger happened, then @@IDENTITY may not > necessarily reflect the record that YOU just updated in YOUR table of > interest. > > So you're possibly better off with IDENT_CURRENT or SCOPE_IDENTITY. > > ---------------------------- > Current session? Consider placing the code for your data into the db where it belongs as a Stored Procedure. --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAJidMY+EvfBbXUH093gX5WQjv50=wgky9ve2bz25onwgv_r...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
