I am fairly sure I already know the answer to this, but any input others may have, or experience would be handy, in case I have overlooked some idea.
Suppose you have a large warehouse system, a combination of SSIS and stored procs, and this system was not built with any form of error handling. This is the start point.
Management wants there to be some "switch to throw" which would cause the entire process to ignore and continue to process on any errors, such as a duplicate key insert.
(We have been over and over all the serious problems with such an idea)
Is there actually such a thing? Or some method which one could copy/paste to every SSIS or stored proc which would suddenly handle the various errors that could possibly happen?
As a note this idea got started because there was an issue with the cube, and the cube was set (originally for a single run) to ignore all errors. So it had a "switch", from the management perspective.
To the best of my knowledge, to handle the errors, we need to change the code, all of the places where it could be a problem to properly handle the errors. That there is no sort of configuration switch at the database or SSIS server level which can be implemented to drop all error records, but continue on and process all non error records.
Any thoughts? (Besides the disaster which looms in the future when ignoring errors entirely)