I am working with a third party program that sends data and files to a web based repository for our customers. I have rewritten the ASP side of things and cleaned that up but we have run across a problem. The internal (3rd party) software when sending files to the repository will either send an INSERT or an UPDATE statement dependent on an unknown (by me or any of the other employees here) setting. I could play with all of the settings and hope I find the one that turns this off. (There are no obvious candidates). What I'd rather do is create a trigger that will, on insert, check to see if there are already records that have the same filename and job ID and update the records instead of creating a new one.
Jump to Post
That sounds like a good idea. Did you have a question or just wanted another opinion on it? I haven't tried to use a trigger like that before and I don't know if the trigger will fire if the SQL Server detects that it is about to violate a UNIQUE …
All 3 Replies
We're a friendly, industry-focused community of 1.21 million developers, IT pros, digital marketers, and technology enthusiasts learning and sharing knowledge.