Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.
MSSQL 2014 Returning GUID on Insert via Stored Procedure
I was wondering what i need to do to get the just inserted GUID from a new Record.
My table has a guid column which has a default value of NewID() . Below is my stored
Procedure. If i can insert just fine but dont get the GUID back
My table has a guid column which has a default value of NewID() . Below is my stored
Procedure. If i can insert just fine but dont get the GUID back
CREATE PROCEDURE tbl_Address_INS
(
@Guid uniqueidentifier OUTPUT,
@Version smallint,
@CustomerId varchar(15),
@CustomerName nchar(32),
@CreatedOn datetime,
@CreatedBy nchar(10)
)
AS
INSERT INTO dbo.tbl_Address (
Version,
CustomerId,
CustomerName,
CreatedOn,
CreatedBy)
VALUES
(
@Version,
@CustomerId,
@CustomerName,
@CreatedOn,
@CreatedBy
)
Who is Participating?
You can get the GUID back by using OUTPUT clause in your SP and this will work when you're inserting multiple records also.
so you will add the command below after your insert but which column name is the actual GUID as I can't see CustomerId varchar(15) holding GUID data.
......
OUTPUT inserted.Guid
......
so you will add the command below after your insert but which column name is the actual GUID as I can't see CustomerId varchar(15) holding GUID data.
......
OUTPUT inserted.Guid
......
So based on your code it seems you are creating a temp table @op and then query @op to get the value ? Is there no way to directly return the inserted.ColGuid
Not realy - is either you declare a variable uniqueidentifier and SET that = NEWID() then insert the value from it then return it at the end OR like in example above that can deal with multiple INSERTed rows in one command.
There are some options where people used triggers(yak!) to PRINT the inserted value but I would never add a trigger on any table (in particular dealing with GUIDS - slowest Microsoft data type - well other than NTEXT) to slow down the insert.
There are some options where people used triggers(yak!) to PRINT the inserted value but I would never add a trigger on any table (in particular dealing with GUIDS - slowest Microsoft data type - well other than NTEXT) to slow down the insert.
Only problem is how to access the returned guid from a vb.net ExecuteNonQuery since it doesn't return
any queryResult only Output Parm
any queryResult only Output Parm
if you want to read the value from a .Net client. you would just use the ExecuteScalar method something like:
...
string sql = "INSERT INTO GuidTest(IntColumn) OUTPUT inserted.GuidColumn VALUES(1)";
SqlCommand cmd = new SqlCommand(sql, conn);
Guid guid = (Guid)cmd.ExecuteScalar();
...
...
string sql = "INSERT INTO GuidTest(IntColumn) OUTPUT inserted.GuidColumn VALUES(1)";
SqlCommand cmd = new SqlCommand(sql, conn);
Guid guid = (Guid)cmd.ExecuteScalar();
...
You can use OUTPUT to return a result set from the stored proc (rather than as an OUTPUT parameter):
CREATE PROCEDURE tbl_Address_INS
(
@Guid uniqueidentifier OUTPUT,
@Version smallint,
@CustomerId varchar(15),
@CustomerName nchar(32),
@CreatedOn datetime,
@CreatedBy nchar(10)
)
AS
INSERT INTO dbo.tbl_Address (
Version,
CustomerId,
CustomerName,
CreatedOn,
CreatedBy)
OUTPUT INSERTED.guid
VALUES
(
@Version,
@CustomerId,
@CustomerName,
@CreatedOn,
@CreatedBy
)
CREATE PROCEDURE tbl_Address_INS
(
@Guid uniqueidentifier OUTPUT,
@Version smallint,
@CustomerId varchar(15),
@CustomerName nchar(32),
@CreatedOn datetime,
@CreatedBy nchar(10)
)
AS
INSERT INTO dbo.tbl_Address (
Version,
CustomerId,
CustomerName,
CreatedOn,
CreatedBy)
OUTPUT INSERTED.guid
VALUES
(
@Version,
@CustomerId,
@CustomerName,
@CreatedOn,
@CreatedBy
)
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
CREATE TABLE dbo.TestTable (
ColGuid uniqueidentifier NOT NULL DEFAULT NewSequentialID(),
Col2 int NOT NULL
)
GO
DECLARE @op TABLE (ColGuid uniqueidentifier)
INSERT INTO dbo.TestTable (Col2)
OUTPUT inserted.ColGuid
INTO @op -- so this is where you put the inserted/generated GUID or GUIDs
VALUES (1)
SELECT * FROM @op -- then you output whether is one or a bunch of them.
SELECT * FROM dbo.TestTable
GO