I consider using an error logging mechanism with sql clr, below are the options:
1) a table within the same database - problem: the context connection sometimes causes exception, and difficult to use.
2) a file system file - seems good, except the file path has to be HARD-CODED, Thus, deployment issue when it is changed.
3) Windwos Event log - required more permission and setup ? anyone confirm this?
I want to find out whether or not it is possible to still log into a table after catching exception that is thrown from inside database or inside SQL CLR. Any idea or links will be very much apprieciated.
Any other options?
View Complete Post