Trigger to perform an insert if record doesn’t exists else perform an update

Question

0.00/5 (No votes)

See more:

I have three Table A (selfid as primary key) , Table B, Table C.

If I update a column value in Table A , the trigger should perform an check operation on Table B and Table C.

If selfid exists in tables then it should only update the column value in tables(B,C).

If selfid doesn’t exists in tables then it should perform an insert operation on tables(B,C).

Posted 6-May-15 3:51am

Member 11669307

Add a Solution

Comments

ZurdoDev 6-May-15 10:03am

Do you have a question? I sure hope it isn't, "Will you do this for me?"

virusstorm 6-May-15 10:05am

I wouldn't do this with a trigger. You will run into a lot of performance issues related to concurrency and locking. I would write a stored procedure to handle this logic.

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)

Dave Kreskowiak · Answer 1 · 2015-05-06T04:20:00

Solution 1

If you've got a list of conditions like this, a trigger is a bad option as they don't scale well. Use a stored procedure instead and have your code call that. The stored procedure can handle all of this and do it without locking the table for any other operation on another request.

Posted 6-May-15 4:20am

Dave Kreskowiak