Getting New Identity value in another Store procedure in sql

Question

0.00/5 (No votes)

See more:

SQL-Server-2008R2

i Have 2 Table named Purchase Master And Purchase detail
and insert record using stored procedure

First i create Store Procedure named Ins_PurchaseMaster (@Parameter....) and Write insert code ...

and after i create Ins_PurchaseDetail (@Parameter....) and Write to code ...

and problem is how to get new Purchase Master Id in Ins_PurchaseDetail SP..... Using Scope_Identity Or @@Identity

Posted 7-Sep-14 22:10pm

Kailashkumar Raghvani

Add a Solution

Comments

_Asif_ 8-Sep-14 4:16am

Well can't you return identity from Ins_PurchaseMaster SP and pass it to Ins_PurchaseDetil SP?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2014-09-07T22:36:00

I would have an OUT parameter to the SP which returns the ID value just created to whatever it was called from. That way, you can pass it through to the next SP.
But...I wouldn't do that in two SP's - I'd want to do it in a single SP with a Transaction - so that if the second INSERT fails, I can roll back the first as well and leave the DB in a "stable" state.