The IDENT_CURRENT() results are not NULL, because its result is based on the table – not the session. The result is NULL because I haven’t inserted anything into an identity column in the new session. Now if I open up a new connection and select again, this is what happens: USE AS AS , Therefore we can use it to find the last identity values for each table.
+-+-+-+Īs mentioned, IDENT_CURRENT() returns its result based on the specified table. | | IDENT_CURRENT('Cats') | IDENT_CURRENT('Dogs') | The returned value is 1, because that’s the last-inserted identity value for this session. Now let’s insert one row into the other table: INSERT Dogs DEFAULT VALUES The current identity value is 2 because I inserted two rows into that table. The SCOPEIDENTITY() function is very similar to IDENTITY in that it also returns the last-inserted identity value in. Here, I create a couple of tables, insert some data, then select the current identity value.
SCRIPTCASE FIND LAST INSERTED ID CODE
The reason this returns NULL is because I opened a new session to SQL Server, and I haven’t yet updated an identity column during my current session.īelow is some code that does some identity column updates. The difference is that SCOPE_IDENTITY() is limited to the current scope. The SCOPE_IDENTITY() function is very similar to in that it also returns the last-inserted identity value in the current session.
This is in contrast to the IDENT_CURRENT() function, which returns the last-inserted identity value for a given table. Note that it returns the last identity value generated in any table in the current session. In SQL Server, you can use the T-SQL system function to return the last-inserted identity value in the current session.
0 kommentar(er)
