Link to home
Start Free TrialLog in
Avatar of sherbug1015
sherbug1015Flag for United States of America

asked on

Returning Identity key from a linked server

I am doing an insert from one server to another linked server.  I need to have the Identity Key returned to me from the linked server.

My statement looks like this:

DECLARE @newids TABLE (id INT)

INSERT  INTO LinkedServer.LinkedDB.dbo.LinkedTable
        ( Column1 ,
          Column2  
         
        )
       OUTPUT INSERTED.MyNewid INTO @newids(id)
        SELECT  Column1 ,
                Column2
               
        FROM    LocalDB.dbo.localtable

I am getting this error:

A remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement.


Does anyone know how I can solve this issue.

Thanks.
ASKER CERTIFIED SOLUTION
Avatar of EugeneZ
EugeneZ
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Something like this:

--Create this procedure on link server
CREATE PROCEDURE <ProcedureName>
AS
BEGIN
      DECLARE @newids TABLE (id INT)
      
    INSERT INTO LinkedDB.dbo.LinkedTable
    ( Column1 ,
      Column2  
       
    )
    OUTPUT INSERTED.MyNewid INTO @newids(id)
    SELECT  Column1 ,
                  Column2
    FROM    ReverseLinkedServer.LocalDB.dbo.localtable

    SELECT id from @newids
END      
GO

--On the local server
DECLARE @newids TABLE (id INT)
Insert into @newids
exec LinkedServer.LinkedDB.dbo.<ProcedureName>
You may want to double check that.  The only way to return an IDENTITY value is as described by EugeneZ.

This is what SQL Server's BOL has to say on the subject:
The scope of the @@IDENTITY function is current session on the local server on which it is executed. This function cannot be applied to remote or linked servers. To obtain an identity value on a different server, execute a stored procedure on that remote or linked server and have that stored procedure (which is executing in the context of the remote or linked server) gather the identity value and return it to the calling connection on the local server.

And yes I realize you are not explicitly using the @@IDENTITY function, but the same applies.
Ah, never mind I see that you are actually following the same approach as EugeneZ suggested.