Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a scenario where i need to Implement triggers for Update and Insert DML Operations.
But,I am in a fix whether to implement Update and Insert in one Trigger or
create 2 triggers for Insert and Delete respectively….
Also,please note that in my case I might need to execute multiple insert commands at one go…
Please suggest me for the better option with regards to performance as CODE OPTIMAZATION is a big issue in my project(i mean my client..!!))..
I would suggest to create a single Trigger as to create a separate trigger for the UPDATE and the INSERT would become maintenance problem. There is no such performance issue regarding the code optimization.
For performance optimization point of view you can check something like
IF EXISTS.