@@identity problem

[poptcat]

Hi.
I have two tables tableA and tableB; both have a primary key (integer data type).
There is a trigger on insert after on tableA. Inside this trigger I put an insert on tableB.
So given the following situation:

insert into tableA....
select @@identity from sys.dummy

the value of identity is changed by that insert inside of the trigger on tableA?
I noticed it's not changed but I can't explain this.
Popa Gabriel

 

[gmmastros]

Try Scope_Identity() instead.

select Scope_Identity() As NewIdentityValue

-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[mrdenny]

Yep. That is the expected behavior of @@IDENTITY. Follow George's example code.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[poptcat]

Thanks for your response. It helped me a lot.