In other words, it will return the last identity value that you explicitly created, rather than any identity that was created by a trigger or a user defined function.

Can User defined function create any identity ? If yes please let me know how. I think UDF can’t perform any DML operation.

in a sinlge transaction stored procedure i want to insert two one records in both the table . like one record in table 1 and get the seed number and insert into second table and i want to return the seed value. so that i can catch it using output paramater direction from .net

like
declare @seedvalue bigint
insert table1(name)values(‘basker’)
set @seedvalue=@@identity
insert table(childname,col1)values(‘baskerchild’,@seedvalue)
return @seedvalue

is this correct?

can i use DML after setting @@identity seed value to any variable ?

please reply

thanks in advance

Thanks

This is related to @@Identity, I want get latest value inserted in table.
But as per this thread @@identity does not give latest value inserted in table

While searching on other sites i got exact and i am sure correct solution, below is the link
http://weblogs.asp.net/esanchez/archive/2006/04/24/443757.aspx#7180719

Solution 1:

CREATE TABLE HumanResources.Employees(
Id int IDENTITY(1,1) NOT NULL,
— Other columns ,
CONSTRAINT [PK_Employees] PRIMARY KEY CLUSTERED (Id ASC)
)
———————————————————————

DECLARE @InsertedRows AS TABLE (Id int)
DECLARE @NewId AS INT

INSERT INTO HumanResources.Employees
( /* column names */)
OUTPUT Inserted.Id INTO @InsertedRows
VALUES (/* column values */)

SELECT @NewId = Id FROM @InsertedRows

Solution 2:
This might helpful..
ex:

Create
( Id int IDENTITY(1,1) NOT NULL,
colname varchar(20)
)

Begin Tran

INSERT into (ColName) values (xxxxxx)

Select max(id) from

End

Solution 2 can work for small kind of data.

Thanks

CREATE TABLE [dbo].[t_TestIdentity](
[TestID] [bigint] IDENTITY(1,1) NOT NULL,
[TestIDCopy] [bigint] NULL,
[TestText] [nvarchar](32) NULL,
CONSTRAINT [PK_TestID] PRIMARY KEY CLUSTERED
([TestID] ASC)
)

GO

INSERT [dbo].[t_TestIdentity] ([TestIDCopy], [TestText]) VALUES (IDENT_CURRENT(‘[dbo].[t_TestIdentity]‘), ‘Test1′)
INSERT [dbo].[t_TestIdentity] ([TestIDCopy], [TestText]) VALUES (SCOPE_IDENTITY(), ‘Test2′)
INSERT [dbo].[t_TestIdentity] ([TestIDCopy], [TestText]) VALUES (@@IDENTITY, ‘Test3′)

SELECT * FROM [dbo].[t_TestIdentity]

TestID TestIDCopy TestText
1 1 Test1
2 1 Test2
3 2 Test3

INSERT INTO MyTable2
(MyColumn1,MyColumn2)
select ‘A’ , ‘B’+MyPk from MyTable1

CREATE TABLE MyTable2
(
MyPK int identity,
MyColumn1 NVARCHAR(100),
MyColumn2 NVARCHAR(100)
)

INSERT INTO MyTable2
(MyColumn1,MyColumn2)
(select ‘A’ , ‘B’ from MyTable1)

Here I’m using select statement to insert records to MyTable2. MyTable1 contains say, 100 records.

now i need to use above to insert a GUID to MyTable2.MyColumn2 by combining MyPk (Current Value).

something like bellow

INSERT INTO MyTable2
(MyColumn1,MyColumn2)
(select ‘A’ , ‘B’+MyPk from MyTable1)

How can I do this? Inserting records should be from a select statement.

Can Scope_Identity(), ident_current() and @@identity gives always 100% correct result?

How to change identity column values (Update) ?

I have a MS SQL 2005 database with a table Test with column ID. ID is a identity column. I have rows in this table and all of them have their corresponding ID autoincremented value.

ID Name
1 abc
2 def
3 ghi
4 jkl

Now I would like to change every ID in this table like this:
ID Name
5001 abc
5002 def
3 ghi
4 jkl

But when I do this I get error:

Cannot update identity column ‘ID’.
I’ve tried with:

ALTER TABLE Test NOCHECK CONSTRAINT ALL
set identity_insert ID OFF/ON
But this does not solve this problem.

Note also that IDENT_CURRENT will only work on the last record inserted on THIS server if the table is merge replicated. Hmmm, I’ve never tried ‘srvr.dbNm.dbo.tbl’ before. I could be wrong about that.

Also, it depends on what you mean by a different server. If you connect to SQL on one server, execute a command that crosses to a different SQL server, that IS a different server.

If you connect to SQL on a different server than the one you are on, that is NOT a different server.

You shouldn’t be doing things directly to a table on a different server anyway. That is a bad security model. Also, that can affect your permission to execute other things that aren’t allowed across servers that become available when you touch them by sproc or func. (Like locking hints.)